Joe works in API.
Anything your systems expose, Joe can call: reading live data before he answers and triggering actions when the customer says yes. He answers the customer and does the API work in the same breath.
400 credits on us for 7 days to decide if he keeps the job.
One conversation. The API work, done live.
Watch the left side: a customer writes in. Watch the right side: API fills itself in as Joe answers. That is the whole product.
Is there a Clio free this weekend?
One automatic left: £78 Saturday to Sunday. Book it?
Yes please, pickup at 9.
Booked for Sat 09:00. Confirmation on its way.
Not a sync. A colleague.
Integrations usually move data after the fact. Joe uses API during the conversation, so the customer gets the answer and the record is already right.
Calls your endpoints with the details collected in the conversation
Reads live data back and uses it in the reply
Triggers any action your systems expose
Real conversations, real records.
“Is there a Clio free this weekend?”
Joe calls your availability endpoint, quotes the live price, and posts the booking back the moment the customer says yes.
“Can I freeze my membership while I travel?”
Joe verifies the member against your API, applies the freeze through the endpoint you expose, and confirms the restart date.
“Where is my order?”
Joe fetches the tracking status from your system and answers with the real ETA instead of a template.
Three steps, no code.
Connect API
One authorisation in the dashboard. No API keys to paste, no middleware to host, nothing to deploy.
Tell Joe when to use it
In plain language, like briefing a new hire: "log every enquiry", "only book in the afternoon diary". No flow charts.
Joe acts mid-conversation
From then on Joe reads and writes in API while the customer is still talking, and the record is done before the goodbye.
Any channel in. API updated.
Whichever way the customer arrives, the API side is handled the same way, with the same rules.
See every channel →Are you open Sunday? I would like a Clio.
Yes, 9 to 6. A Clio is £78 for the day. Shall I book it?
Need a quote on 3 vans for two weeks in August.
Quote sent. 3 vans, 14 days, with the long term discount.
How much for a deep clean on a 3 bed?
£185, or £155 with a monthly visit. Saturday is free.
Running late, can I move my 3pm?
Moved to 4:30 and confirmed. See you then.
Do you cover Bordeaux for a monthly garden contract?
We do. A monthly contract starts at £89. Want the details?
Is the brunch menu on today?
It is, until 3. Want me to book you a table for two?
I need a refund of £240.
Refunds over £200 go to the team. Passing you over now.
I would like to reschedule my delivery.
Done, moved to Thursday morning. Anything else?
Do you take on agency partnerships?
We do. I can set up a call with the team this week.
Where do I buy this kit?
Link is in the description. Ships in 48 hours.
What is the price for the annual plan?
£1,490 with the yearly discount, from the price list.
Has order 4512 shipped?
Yes, this morning. Tracking sent to the customer.
Do you ship to Ireland?
We do, 2 to 3 days. Want the checkout link?
API questions, answered.
Do I need to build a flow to connect API?
No. You connect API once and describe in plain language when Joe should use it. He decides in the conversation, the way a colleague would, so there is no canvas of nodes to maintain when things change.
What if API is unavailable?
Joe still answers the customer. The action is retried, and if it cannot complete he escalates to your team with the full conversation attached, so nothing is silently lost.
Can I control what Joe is allowed to do in API?
Yes. You set the rules: what he may read, what he may write, and what always goes to a person first. You can require approval before any action.
How long does setup take?
Connecting a tool takes a couple of minutes. Most businesses are live, answering and acting, in about twenty minutes total.
Joe's ready. Are you?
Connect API this afternoon. The first record writes itself tonight.
400 credits on us for 7 days to decide if he keeps the job.