Phone preview. Live setup comes later.
Meet the next voice at your venue.
Explore receptionists, routing and accountable callbacks in one workspace. Phone is a preview product; live calls stay off until provider setup and acceptance are complete.
Available in preview
Preview workspace access to receptionist drafts, routing, readiness and callback controls, with a local text simulation. Live setup comes later; provider acceptance is required before receiving real calls.
See what’s nextBrowse fictional Phone readiness, receptionist drafts and callbacks. Live transport remains off; these sample records do not demonstrate provider acceptance.
Current workspace layouts with sample data. Nothing is saved or sent.
Phone · Preview
Live setup comes later. Provider acceptance is required before real calls; these records are fictional.
Service readiness
Preview access does not activate a live line.
A saved draft does not verify a real call or provider connection.
Explore the current Phone layout with fictional records. Search, switch views and try both themes. Nothing is saved, sent or charged.
On the other side of the shift
Less friction. More getting on with it.
- 01
Prepare a receptionist before connecting a number.
- 02
Keep callback ownership and outcomes with the original call.
- 03
Review which connected products are ready and permitted.
What’s included
Made for the job.
The practical details behind the promise. Built around the people doing the work, and connected to the information they need.
- 01
Receptionist drafts
Prepare the greeting, instructions and staff destination. Saving and publishing are separate actions; text simulation has no provider effects.
- 02
Calls and callbacks
Review authorized call summaries and assign follow-up with a due time and a recorded outcome. Recording and transcript access stay separately controlled.
- 03
Connected source records
Optional Bookings, Ticketing, CRM and Inbox connections retain their own setup and permissions. A booking hold or guest link never counts as a confirmed reservation.
- 04
Visible setup requirements
Review number, routing, provider and spending-cap readiness. Enabling the preview does not connect a live line, purchase a number or activate a payment service.
More of the working product
What you can do with Phone.
Explore the tools behind the overview, then open a workflow for the steps, settings and availability that apply. Product access, rollout and connected providers determine what your workspace can use.
Receptionist authoring
- Draft the greeting, approved caller information and routing instructions.
- Rehearse with a fixed text simulation.
- Save drafts and publish versions separately.
Call service
- Review call summaries and their timeline.
- Open transcripts or recordings only with the relevant access.
- Assign callbacks with due times and recorded outcomes.
Routing
- Choose an approved staff destination.
- Distinguish accepted transfers from a successfully connected call.
- Retain callback fallback and PBX rollback instructions.
Connected guest work
- Provide public Event information and the correct purchase link.
- Use permitted Bookings availability and a private continuation link.
- Keep guest verification and payment checkout outside the call and model.
Privacy
- Set the supported content-retention policy.
- Export or erase retained content with a recorded reason.
- Track provider deletion retries separately from booking evidence.
Commercial control
- Review number and provider readiness.
- Set an explicitly approved spending cap.
- Keep business Phone charges separate from guest purchases.
Preview. Live calling remains disabled until provider acceptance. Text rehearsal does not test live voice, Bookings availability or a staff transfer.
Explore every workflow in the guides.
Choose a guide to see all its topics. The detailed guides include setup requirements, preview features and supported limits.
Phone4 workflow topics
Preview reception, call routing, callbacks and verified guest booking continuations; provider activation is separate.
Read the complete guidePart of the bigger picture
The context comes with it.
The guest, the venue, the team. Useful information should follow the work. Phone connects to shared records, with access controlled for your organisation and your people.
A clear picture
Today. And what’s next.
Preview workspace access to receptionist drafts, routing, readiness and callback controls, with a local text simulation. Live setup comes later; provider acceptance is required before receiving real calls.
Complete an approved pilot covering real calls, consent, staff transfer, independent fallback, private booking links and provider billing before live activation. Existing-line forwarding needs its own verification.
Good questions
Phone FAQs.
Can Phone answer my venue's number today?
No. This release makes Phone available as a preview product. Live calls stay off until the dedicated gateway, provider account, number, billing and real-call acceptance are approved.
Does enabling Phone buy a number or start charging?
No. Enabling the preview is separate from number purchasing and live activation. Provider setup, reviewed commercial terms and an explicit spending cap are separate steps.
Does Phone need every other Soupy module?
No. Bookings, Ticketing, CRM and Inbox are optional connections. Their source permissions and availability still apply; Phone does not enable them automatically.
What can I try in this tour?
Browse fictional readiness, receptionist and callback records. The tour makes no calls, sends no messages, creates no bookings and takes no payments.
Start with the pressure point