The process is real, and nobody else’s
A property company that needs maintenance intake, vendor rules, and tenant messaging as one design — not three chat widgets.
Specialized
Custom AI for the work that does not fit a receptionist template.
Use this when the work is real and repetitive but is not ‘answer the phone.’ Interviewers, internal routing, multi-location rules, custom APIs, and multi-agent setups live here. Scope comes from discovery — not from a slide that says we automate anything.
Receptionist and answering workflows are the common starting point. Custom is for operations that need extra agents, deeper integrations, or unique rules. Whether a given system can be connected depends on its API, webhooks, and access.
Elliot is a receptionist you can talk to now. Custom automation starts with a working session about the process, not a demo of a template.
What ‘custom’ actually means here
A designed system after we have seen the work. Not a box of plugins.
Workflows unique to one company
Vendor routing, multi-office hours, internal alerts when a condition is met, role-specific agents.
Connections where they can be built safely
API, webhook, or supported integration. Confirmed in discovery. Not assumed in this sentence.
Multiple agents and roles
Typical on Custom plans: a receptionist plus something that is not a receptionist.
Human-in-the-loop steps you define
Automation that stops for a signature, a review, or a judgment call is still automation.
When a template is the wrong product
Systems that do not talk to each other
Staff retype the same job into two tools. Sometimes an API can help. Sometimes it cannot. Honesty first.
A receptionist is not enough
The phone is fine. The broken part is everything after the call.
How EXCEL takes on custom work
Discovery is not a sales hurdle. It is how we keep from promising a connection that does not exist.
01
Map the process
Who does what today, which tools, which exceptions, which steps must stay human.
02
Decide what is in
Testable, appropriate, approved. The rest stays with people.
03
Build and connect
Agents, rules, and only the integrations that survived the map.
04
Test edge cases
Then launch. Then change it when the business changes.
Hypothetical: multi-location clinic routing
Illustrative operations design. Not a claim that every EHR or PMS can be connected.
The problem
Three offices, different hours, different providers, one main number. Callers get the wrong location’s rules.
The design
A receptionist layer identifies location, then applies that office’s hours and escalation tree. Booking only if that office’s calendar can be connected.
The stop
Clinical questions still go to staff. The automation is routing and hours — not medicine.
The honesty
If the practice-management tool has no safe API, booking stays a structured request. That is discovered before a contract pretends otherwise.
Custom versus ‘we’ll automate anything’
A responsible build has a no-list.
Not every idea should be automated
Counseling families, binding insurance, diagnosing equipment, making employment decisions — those stay with people.
Integrations are evidence-based
Custom API work lives on the Custom plan. Feasibility depends on the other system. We say so before we promise.
Often the second project, not the first
Many companies start with a receptionist, then come back when the leftover process is obvious.
What discovery has to produce
- A written process, including exceptions
- Systems of record and whether they can be reached
- Which agent roles exist, and which person they escalate to
- Success criteria that are observable, not slogans
Judgment, signatures, and anything unsafe to guess
If a step needs a licensed professional, a manager, or a human relationship, it stays there. The automation should make that handoff cleaner, not skip it.
Custom API integrations are in the Custom plan. Whether a given system can be connected depends on its API, webhooks, and access — confirmed in discovery, not assumed here.
Plan details live on the pricing page. Current plans are listed there.
Industry overviews
Industry overviews live on their own pages. Dedicated workflows, when they exist, are linked below.
Guides related to this service
Related guides for the problems this service is built to solve.
Related EXCEL services
- AI ReceptionistA custom AI receptionist that answers calls, handles approved questions, captures leads, routes callers, and supports scheduling around how the business already works.
- AI Interview AgentScreens applicants, runs first-round interviews with role-specific questions, and records responses so hiring can move without a calendar pile-up.
- AI Customer Service AgentCustomer-service AI that answers approved policy and service questions and escalates anything that needs a person.
Questions buyers actually ask
Is every business a custom build?
Receptionist and answering workflows are the common starting point. Custom is for extra agents, deeper integrations, or unique rules.
Do you automate anything we describe?
Only where it is appropriate, testable, and approved. Discovery decides what should stay with people.
Can you connect to our software?
Sometimes. It depends on APIs, webhooks, and access. That is confirmed in discovery, not claimed on this page.
Is this the Custom plan?
Often yes — multiple agents, custom APIs, and broader automation typically sit on Custom. See live pricing, then scope the work.
How long does a custom build take?
It depends on the process and the connections. We will not put a fake average on this page. A consultation is how you get a real range.
What is a good first custom project?
A repetitive process you can describe on a whiteboard, with a clear human fallback. Vague ‘make the business run itself’ is not a project.
If the process is repetitive and specific to how you operate, we design around that — not a template.
Bring the real call types, the real software, and the rules you already use. We will tell you what belongs in an agent and what should stay with people.