Customers
Inbound
Every inbound channel answered the moment it lands, qualified against rules you wrote, and booked — not queued for someone to get to.
The operating model
Rules you wrote.
Decisions you can audit.
Sophia is run, not licensed. JOOLT configures the operation with your team, operates it, and stays accountable for it — and every decision it makes is recorded against the rule that produced it.
Talk to us
a 15-minute call — no checkout, nothing to buy online
Before the conversation: Start the assessment
A person, always. Sophia escalates rather than guesses.
01 · The engagement
From a call to a running desk.
01
We learn how the outside world reaches you
Which channels carry real volume, what arrives on them, who currently handles it, and where things are being dropped. This is a conversation with the people doing the work, not a form.
02
Your team writes the rules
What qualifies. What never qualifies. What must reach a named person and how fast. The rules are yours, in your words — Sophia holds them, she does not invent them. Where nothing is written, the default is to protect rather than guess.
03
Channels and systems are connected
Phone, messaging, email, calendar, CRM and billing are wired to the desk by JOOLT during onboarding. Your team keeps the tools it already uses; nothing is migrated to make Sophia work.
04
The desk goes live
Inbound is answered where it arrived, on arrival. Every item resolves against the rules rather than sitting in a queue waiting for capacity.
05
The rules keep moving
Every operation discovers in month two that it wanted something escalated differently. Tuning the rules is part of running the operation, not a change request with a quote attached.
02 · The decision
Four outcomes. There is no fifth.
This is the part that separates an operation from a chatbot. Every inbound item lands in exactly one of these, and the rule that put it there is recorded alongside it.
One inbound item, four possible endings
An inbound item arrives
Any channel. Screened against the rules your team wrote.
resolves to exactly one of
Protect
Below the bar. Still answered.
Hold
Incomplete. Held with a draft.
Handle
Routine. Answered and filed.
Escalate
Earned it, or ambiguous. Goes to a person.
There is no fifth outcome, and no state where an item is neither resolved nor owned. Whichever ending applies, the rule that produced it is recorded alongside it.
Shown at equal weight deliberately. How real inbound distributes across the four depends entirely on the rules you write, so drawing this as a funnel would imply a measurement we have not made.
Four inbounds, one desk, four different endings Worked example
Below the bar, and still answered
A cold pitch that matches nothing your team asked for. It never reaches a person — but it does get a reply, because silence is how a sender decides to try again through somebody else.
Real, but missing a piece
A genuine enquiry with one thing absent. It is not guessed at and not binned: it is held, with a draft asking for exactly what is missing. If the answer arrives, it moves on its own.
Routine, so it is simply done
A question your rules already answer. Handled in your company's voice, filed to the contact record, and the next conversation starts knowing this one happened.
It clears the bar, so a person gets it
Not a notification. The named owner receives it with the reason it cleared, the rule that decided, and the history attached — which is the difference between escalation and forwarding.
Cold email · 6:12 am
“Quick one — are you the right person for our partnership programme? Happy to send a deck.”
Unsolicited partnership approaches are not routed to the team. Answer, do not forward.
Protect · declined warmly, nobody interrupted
Web form · 7:48 am
“We need cover across several of our sites starting next month. Can you help?”
Multi-site enquiries require the site count before routing. Do not assume it.
Hold · draft sent asking for the one missing detail
Text message · 9:03 am
“Is Thursday still on, and do we need to be on site for it?”
Booking confirmations and attendance questions are answered from the calendar record.
Handle · answered and filed to the contact
Call · 9:31 am
An existing customer’s procurement lead, asking to bring forward a renewal that is already in motion.
Named accounts reach their owner the same day. Renewal timing is never negotiated at the desk.
Escalate · to the named owner, with the reason attached
There is no fifth ending. Every item above resolved, and each one carries the rule that resolved it — which is what makes the operation reviewable afterwards instead of something you have to take on trust.
A worked example of the shipped four-outcome ladder, not captured traffic. The outcomes and their order are the real ones; the four inbounds, the rules and the times are written for this page, and no customer, company or figure appears in any of them.
Protect
Below the bar, or not a real approach. Kept off your team's plate entirely — but still answered, so nobody is left hanging.
Hold
Real but incomplete. Held with the reason it was held and a draft asking for exactly what is missing. If the missing piece arrives, it moves.
Handle
Routine and clear. Answered in your company's voice and filed to the record, so the next conversation carries this one.
Escalate
Genuinely cleared the bar, or genuinely ambiguous. Reaches a named human now, with the reason attached — never a bare notification.
What “escalated” actually does
Sophia escalates
She has hit the edge of what she was given, and does not guess past it.
first touch — text and email, deliberately not a call
The item goes to the person who owns it
Not to a queue and not to a shared inbox — to a named human, with the original message and the reason it was escalated already attached.
then one of two things happens
They reply
Sophia writes the answer back to the sender in their voice, grounded only on the original message and their reply, and closes the record.
They do not
At four hours, one call and one follow-up — once, never on a loop. Still nothing, and it holds on the desk with a digest rather than being dropped.
Paused is not the same as unreachable. When a principal has alerts paused, the routine nudge waits on the desk instead of chasing them — and a genuine emergency still rings through.
The two numerals here are policy constants in our own codebase, not performance claims. Nothing on this page states how often escalation happens or how fast anyone replies, because those depend on your rules and your people, and we have not measured them for you.
03 · What she will not do
The boundaries are the product.
Most of what makes Sophia safe to put in front of your customers is what she refuses to do. These limits are enforced in code, not left to good behaviour.
An operation you cannot bound is one you cannot deploy.
She does not invent
Answers come from what you gave her. Anything that would require information she does not hold escalates instead of being guessed at.
She does not take instructions from inbound
A message from outside is data, never a command. Rules come only from your configuration — a boundary checked on every push to the codebase.
She does not negotiate your floor down
Repeated pressure below a threshold you set produces a firm decline and an escalation, never a softening.
She does not commit you
Authority is a narrow, explicit list of things she may agree to. Everything outside it goes to a person.
How these are enforced, with the code that implements each one, is set out on Security & Trust.
04 · Where it applies
The same model, four counterparties.
Prospects
Sales Support
The follow-through around your reps — pipeline kept current, quotes and invoices raised, and follow-up that actually happens.
The executive's own inbound
Executive Support
A desk in front of a leader's inbound: every approach screened against a bar they wrote, and only what earns it reaches them.
Other companies' agents
Agent-to-Agent
An authenticated endpoint where another company's agent can put a structured proposal to yours and get a bounded, grounded decision back.
05 · Before anyone discusses terms
Start with where you stand.
Everything else here opens on a conversation. This does not. It is the first piece of real work rather than a brochure — the current position, written down, so the conversation afterwards starts from a shared set of facts instead of a pitch.
The assessment models what the front office is costing in your industry, layer by layer, and sets out the order it would be put right in.
- Where the work is leaking, layer by layer — inbound that is never answered, follow-up that never goes out, enquiries that never convert, scheduling, and the review cycle. Each one is modelled separately rather than rolled into a single number.
- The order it would be fixed in: a phased plan over the first ninety days, what Sophia would take first, and what deliberately stays with your team.
- The part that is not financial — the hours, the interruptions and the weekends the current arrangement costs, set out rather than alluded to.
- It is written the moment you submit it and it is yours: on screen immediately, and in your inbox. No call is required to unlock it and nobody phones you about it.
The promise
Every channel answered. Every decision made.
Talk to us
a 15-minute call — no checkout, nothing to buy online
Before the conversation: Start the assessment