Pricing
Talk to the team
Solutions

Three ways customers stop clicking.

The job changes by sector, but the shape is the same: someone asks for an outcome, and something has to go and get it.

SaaS and developer tools
Answers, not dashboards

Your users came for an answer, not a report builder.

Most of what people do in a SaaS product is assembly: filter, sort, export, pivot, and hope the total is right. When they can ask instead, the interface stops being the work.

Convoy exposes the queries and the actions your product already supports, scoped to what each person is allowed to see, so an assistant can answer inside your app or from wherever they asked.

“How much overtime did the evening team run last month, and which week was worst?”Answered from live timesheets, scoped to the teams that manager may see.
01OnboardingGetting set up becomes a conversation instead of a checklist nobody finishes.
02Support deflectionThe answer is in your own data, so it arrives before a ticket is opened.
03In-product actionsChanges made through your rules, with approval where the change costs money.
Human navigationLegacy
app.shiftly.io/schedule
ScheduleTimesheetsReportsRequests
Evening teamWeek 14All sitesExport
MonTueWedThuFriA. DialloM. CostaR. HaddadL. Meyer
ShiftOvertimeOff

Read the grid week by week, switch to Timesheets, export four CSVs, pivot them in a spreadsheet, and hope you added it up right.

Agentic navigationConvoy
In Shiftly, how much overtime did the evening team run last month, and which week was worst?
Working
  • Resolved Shiftly to its Convoy interface
  • Called get_timesheets — team: Evening, 1–30 April
  • Compared scheduled against actual hours, week by week
  • Scoped to the teams this manager is allowed to see
Overtime by weekApril
020h41hW1W2W3W4
Total overtime107 h across 4 weeks
Worst weekW3, 41 h
Main driver3 uncovered late shifts
Applied rulesTeam scope, no personal data

One question. Real timesheets, the answer drawn, and only the teams they are allowed to see.

Services and booking
Qualify, book, follow up

The right slot matters more than the first free one.

Booking sites hide the thing that decides the booking. Which practitioner, which speciality, whether the insurance covers it. People scan a grid and guess.

Convoy lets an agent ask what actually matters, match against it, check the constraints, and hold the slot — with your cancellation policy and intake rules attached from the start.

“Book me a physio near King's Cross this week, an evening slot, with someone who treats runners' knees.”Matched by speciality, checked against cover, then held.
01QualificationThe questions you would ask on the phone, asked before the slot is taken.
02BookingReal availability, not a request form that someone answers tomorrow.
03Follow upReminders, rescheduling and repeat visits handled in the same thread.
Human navigationLegacy
lumen-physio.co.uk/book
PhysioSports massageRehabPilates
This weekEveningsKing's CrossInsurance
Mon18:00
Tue19:30
Wed18:30
Thu19:00
Thu20:00
Fri18:00
Fri19:30
Sat09:30

Pick a service, scan a grid of slots, open each practitioner to check the speciality, then start again when the slot is gone.

Agentic navigationConvoy
Book me a physio near King's Cross this week, an evening slot, with someone who treats runners' knees.
Working
  • Resolved Lumen Physio to its Convoy interface
  • Called search_availability — evenings, this week, N1
  • Matched practitioners by speciality, not by first free slot
  • Checked insurance cover, then held the slot
AO
Amara O.
Sports physio
Thursday 19:0050 min
SpecialityRunning injuries
CoverInsurer accepted, £12 excess
Applied rulesCancellation policy, first visit form

One call. Real availability, the right practitioner, your policies attached.

Retail and commerce
Find, decide, order

The catalogue is there. The answer is not.

A shopper lands on a category, stacks four filters, opens three products, checks delivery, and starts again. Everything they needed was on the site. None of it was an answer.

Convoy puts your catalogue, stock and delivery rules behind one question, so a shopper — or the assistant they sent — gets a product and a date instead of a results page.

“Order me an organic olive oil under 10 euros, delivered tomorrow in Lyon.”One call against live stock, your pricing rules and your voice.
01DiscoveryFound and recommended where your customers are already asking.
02DecisionAdvice against your real range, not a generic answer about the category.
03Order and afterStock, delivery windows and tracking, in the same conversation.
Human navigationLegacy
terretable.fr/huiles
HuilesÉpicerieConservesCoffrets
BioMoins de 10 €500 mlLivraison LyonTrier : prix
Huile d'olive vierge extra8,90 €
Huile de noix12,40 €
Huile de colza7,20 €
Olive & citron9,60 €
Huile de sésame11,00 €
Olive AOP Nyons14,50 €

Land on the shop, pick a category, stack four filters, open three products, check delivery, then start again. The catalogue is there. The answer is not.

Agentic navigationConvoy
Order me an organic olive oil from Terre & Table, under 10 euros, delivered tomorrow in Lyon.
Working
  • Resolved Terre & Table to its Convoy interface
  • Called search_products — olive oil, organic, ≤ 10 €
  • Checked live stock and delivery windows for Lyon 7
Terre & Table
500 ml
Extra virgin, organic 500ml8,90 €
StockIn stock, Lyon 7
DeliveryTomorrow before 14:00

One call. Real inventory, your rules, your voice.