Enterprise DNA

Instead of Chili Piper

Stop renting Chili Piper. Own your lead routing system.

We build your version around your territories, representatives and handoff rules. We map your Chili Piper routing data and agree the live connections your business needs.

Chili Piper starts at $1,250 a month, billed annually: $15,000 a year for Routing & Scheduling. Prices use the vendor’s dollar notation.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The subscription

What the Chili Piper bill covers

Compare the published package with the work your team actually needs. The free base shown below handles your local routing record. Live intake, calendar booking and customer-system connections are agreed separately.

receipt_long

An annual starting commitment

Routing & Scheduling starts at $15,000 a year. Monthly billing is not offered for these plans.

groups

An included seat allowance

The starting package includes up to fifteen seats. Extra Routing & Scheduling seats are $45 each per month.

alt_route

Inbound distribution

The package includes record routing and round-robin assignment. Your territories, people and capacity determine who receives the next enquiry.

event

A calendar service

Scheduling sits beside routing in the package. Identify which booking connections your team needs in its owned version.

chat_bubble

Web experiences

Experiences starts at $3,500 a month. Compare that broader service with the routing work you want to own.

database

Your operating record

Keep the enquiry, matching territory, assigned owner, acceptance and review dates together under your own rules.

The owned version

A routing decision you can explain

Assign

Know why each enquiry goes to that person

Ordered territory rules produce a named destination and an explanation before you commit an assignment.

  • check Compare the country and other supplied attributes
  • check Read the first matching territory
  • check Check that the representative is available
  • check Hold an enquiry when the destination is full

Balance

Work with the capacity you actually have

See active work alongside the limits you set for each representative.

  • check Count assigned and accepted enquiries
  • check Exclude unavailable representatives from new work
  • check Rotate a team by its oldest recorded assignment
  • check Keep existing ownership when routing rules change

Follow through

Catch the handoff that never happened

A recorded assignment and an accepted handoff are separate events.

  • check Set a deadline when an enquiry arrives
  • check Find enquiries still waiting for an owner
  • check Record the assigned person’s actual acceptance
  • check Close accepted work with the supplied outcome

Review

Ask across your own operating rules

Combine routing, workload and retention checks in one weekly review.

  • check Find overdue handoffs owned by unavailable people
  • check See which countries in your queue have no route
  • check Review enquiry details past your chosen review date
  • check Draft handoffs and decision records in your brand

Make it yours

Design your own Chili Piper replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Chili Piper. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Chili Piper replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Chili Piper data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Lead Routing for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Lead Routing for Claude Code

Connected to your own database

Which enquiries need an owner or an accepted handoff?

ENQ-105

Name
Old enquiry for review
Status
assigned
Owner
Alex Reed
Due_at
2026-05-03T02:21:04.464Z
Reason
Handoff not accepted

ENQ-102

Name
Harbour Systems
Status
assigned
Owner
Mere Rangi
Due_at
2026-10-26T02:21:04.464Z
Reason
Handoff not accepted

ENQ-101

Name
Kauri Analytics
Status
new
Due_at
2026-10-27T02:21:04.464Z
Reason
No assignment

ENQ-104

Name
Pacific Instruments
Status
new
Due_at
2026-10-30T02:21:04.464Z
Reason
No assignment

Ask it anything

Questions your own routing records answer

Ten questions answered from your enquiries, capacity rules and recorded decisions.

chat_bubble Which unassigned enquiries have already missed our handoff deadline?
chat_bubble Which countries have no matching route in our current enquiry list?
chat_bubble Which matching routes are blocked by representative capacity?
chat_bubble Which unavailable representatives still own open enquiries?
chat_bubble Who has the most open enquiries and overdue handoffs together?
chat_bubble Which enquiries are still awaiting a named owner?
chat_bubble Which enquiries need a retention review under our chosen policy?
chat_bubble Who recorded each assignment and what reason did they give?
chat_bubble Which imported routing version came from this source digest?
chat_bubble What changed in availability, ownership or handoff acceptance this week?

Switching

How to switch from Chili Piper

A move usually involves exporting your routing assignments, mapping your rules and destinations, then checking the new record alongside Chili Piper before you switch.

  1. 1

    Export your assignment data

    Use the native assignment export Chili Piper provides. Export the routing values and destinations you want to keep. If your account offers a choice of formats, use what it allows, usually CSV or Excel, and check with Chili Piper if the export path or format is unclear. This export does not bring across your full operating history or connected workflows.

  2. 2

    Trial the import

    Have the export loaded as a trial first. The trial checks the input without writing records, so use it to catch problems before bringing anything in. Once the file passes, import it as an inactive routing version. It will not become the routing version you use until you review and activate it.

  3. 3

    Review the import results

    Check the row counts and the reasons given for malformed or unsupported input. The import stops when it finds either. Confirm that the source values are mapped to the right matching conditions and destinations. Correct any gaps in the export or mapping, then trial and load it again before you treat the version as ready.

  4. 4

    Run both systems side by side

    Keep Chili Piper in use while you compare route decisions and handoffs with the new process. Test the routing you rely on, and separately test any calendar, intake, customer system or notification connections you need. The free base works on local records and does not provide those connections by itself. Do not switch live work until your checks pass.

  5. 5

    Switch off Chili Piper

    Once you have checked the routing version and the connections your business needs, make the new process the one your team uses. Then stop using Chili Piper and cancel it according to your account terms. Keep an agreed backup of your records and make sure the new process has the operating controls it needs.

construction

Where the real effort goes

The real work is usually mapping your own fields, territories, matching conditions and destinations, then deciding how much enquiry history and which meeting records to bring. History, calendar settings and wider workflows need separate migration work. When Enterprise DNA installs and runs your version, it maps and checks the agreed scope with you and builds the rules and connections you need.

Not ready for a call?

Get your Chili Piper switch plan by email

We will send you the step-by-step plan for moving your business off Chili Piper, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Do it yourself, customise it, or have us run it

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install
  2. 2 Run npm run demo with the fictional enquiries
  3. 3 Open the folder in Claude Code, Codex, OpenCode or Cursor
  4. 4 Trial your Chili Piper Assignment Table CSV with an explicit mapping, then review before activation
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your territories, capacity limits and acceptance rules
  • check Your Chili Piper routing data mapped and checked
  • check A web front end or a different technology stack if you want one
  • check Intake, calendar and customer-system connections built to the agreed scope
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Your agreed connections maintained and checked
  • check Your backup and access responsibilities agreed from the start
  • check Your reports and operating rules adapted as the business changes
Talk to Sam

Questions

Instead of Chili Piper, answered

Does the free version replace everything Chili Piper does? expand_more

It runs the local enquiry routing and handoff record shown here. Calendar booking, automatic intake and live customer-system updates are separate connections. Enterprise DNA builds and tests the connections you need as part of your version.

Can we bring our existing routing data across? expand_more

Yes. Chili Piper provides an assignment export. The free version reads its routing values and destinations with an explicit mapping of your matching conditions. Your enquiry history, calendar settings and wider workflow need separate migration work. Enterprise DNA maps and checks that scope with you.

What happens if nobody has room for the next enquiry? expand_more

The enquiry is held for review with the matching territory recorded in the preview. It is not silently passed to another territory. You can see availability, active workload and capacity before recording an assignment.

How does this compare with LeanData or staying on Chili Piper? expand_more

Chili Piper and LeanData both provide routing services. Start with the live connections you use and the yearly bill you pay. This free base gives you an owned local record. Enterprise DNA agrees the migration and connected service your business needs before a switch.

What does Enterprise DNA charge and who looks after it? expand_more

One setup fee, then a monthly retainer, agreed around your scope. We bring across the agreed records, build your operating rules and connections, and run your version through Omni by Enterprise DNA. Your database remains yours.

Put your routing bill beside your actual workflow

Book 30 minutes with Sam. Bring your Chili Piper bill and a typical enquiry journey. We will work through your routing rules, the connections you need and what your own version would involve.

Book a discovery call Get the free version

Lead Routing for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Chili Piper?

Get your version built