Contact
Request a pilot.
Six fields, and none of them are about your customers. Tell us what your team spends the most call time on, and a person reads it and replies with next steps.
What happens after you press the button
-
Your request reaches a person
Not a scheduler and not an automated sequence. Somebody reads what you wrote. If the form tells you the request was received, it is because the request was actually stored — the message never appears on a hope.
-
A human replies with next steps
By email, to the address you gave. The reply says what we think your workflow would involve, which connections it would need, and where it would stop and hand to a person.
-
A time is confirmed with you
If a conversation makes sense, we agree a time together in that email exchange. Nothing is on anyone’s calendar until you have said yes to a specific time.
Before you send it
Three things worth knowing, so the reply is not a surprise:
- There is no price list yet. Pricing explains every line a quote will carry and why none of them has a number in it.
- Almost every system connection is still Requires verification. Integrations shows exactly which is which.
- Several data-handling questions are open, including retention. The register of unconfirmed items lists all of them, with owners.
Not a pilot request?
The same form is the route for anything else, including a data request. Choose the industry that fits, send it, and reply to the email you get back with the detail — that way nothing sensitive goes into a web form in the first place. The current position on deletion requests is on data handling and controls.
