Every request in your own form, with every detail.
Quote, technician visit, complaint: the agent picks the right form, asks each field one at a time, reads the request back and sends it to your team as soon as the customer confirms it.
Hello, the air conditioner is not cooling and it is leaking water.
I'm sorry to hear that. Let's book a technician visit. What model is it?
Confirmed by the customer, email and webhook sent
How it works
The forms are yours: up to 10 request types, each with its own fields.
- 1
The customer explains
By phone or in the chat.
- 2
The right form
The agent works out what kind of request it is.
- 3
One field at a time
Required fields, choices from a list, dates.
- 4
Confirmed and sent
Email and webhook with every answer.
Forms that fit your work
No code, from the agent's Tools tab.
Request types
One type for each kind of request, with a name and a sentence on when it applies.
Your fields
Text, number, date, phone, email or a choice from a list, with required fields and instructions.
Customer details
You decide what each request needs so your team can get back to the customer.
Email and webhook
Every request arrives at once, and can be sent again from the app whenever needed.
Status
The team follows every request: new, in progress, completed or cancelled.
Testing
A scenario runs the whole request. A test request is never filed or sent.
The Requests app
Requests today and this week, the open ones, requests by type and the list with search and filters.
Frequently asked questions
Can I have a different form for each kind of request?
Yes, up to 10 types. The agent picks the right one from what the customer says.
Where do the requests go?
To your email, to your system by webhook and to the Requests app in the console, with an Excel export.
What if the customer does not know an answer?
A field that is not required stays empty. For a required one the agent asks again in other words.
No request gets lost on a sticky note
Build your first form and try it in a few minutes.