Administration
Your opening hours serve online booking, the phone system and the chatbot. Your logo serves quotes, emails and the booking page. Describing them once per module gives you three truths that drift apart. Here they are described once.
No credit card required
How it works
The company profile, its representatives, its documents, its branding and its workspaces. This is what appears on a quote, in an email, on a booking page and at the foot of a form: an address corrected here is corrected everywhere, including on documents already templated.
Availability schedules are shared: the same schedule closes the calendar, sends the phone system to voicemail and puts the chatbot in out-of-hours mode. Sender domains and authorised senders decide what goes out, and from which address.
Roles are made of individual permissions, API keys each carry their own scope, and single sign-on connects your corporate directory. This is not a screen of checkboxes: it is the same permission catalogue that the interface, the public API and every service obey.
Retention periods are set per type of data, within the bounds we publish. Credits, consumption, licences and billing live in the same place: knowing what you consume and knowing what you keep are two administrator questions, not two tools.
Use cases
Detailed scenarios with figures, where this hub plays a central role: the starting situation, what gets put in place, what it shifts.
4,200 policies, 11 staff, and 9% of cancellations nobody saw coming.
Discover Local government19 municipalities, one front door for residents.
Discover Housing12,000 homes, and a complaint that no longer vanishes between caretaker and contractor.
DiscoverFAQ
Those you give the permission to, and nothing more. Access is not a single switch: you can hand billing to one person, roles to another, and leave opening hours to whoever runs the schedule.
It depends on the setting, and that is deliberate. Branding and opening hours can differ per workspace; roles, API keys and single sign-on apply to the account. A municipal department can have its own identity without having its own access policy.
Yes. Two read-only logs trace sensitive changes: one for roles and permissions, the other for account resources such as API keys and single sign-on. No endpoint allows a line to be deleted.
No. Everything has a sensible default, and an account works without ever opening this screen. You come to it when a question arises — “why did this email go out from that address?”, “who deleted this role?” — and the answer is here.
Some of them, yes, with an API key whose scope is explicit. The developer documentation lists the available routes and the permissions they require.
Another question? Write to us — a human will answer.
Create your free account in two minutes: CRM, telephony, marketing, appointments and customer service — all in one place, with AI built in.
No credit card required
