Forms whose answers
an agent picks up first.
Bug reports, requests and surveys whose answers land in the workspace as work. An agent reads each one as it arrives, routes it to the person it belongs to and asks the sender for whatever is missing.
Forms
What it does
Described, then built
Say what you need to collect and an agent drafts the form. Adjust the questions, the logic and who may answer.
Answers land as work
A bug report becomes a row in the support sheet, a purchase request a task, a survey answer a message in the channel that asked.
Routed by an agent
Billing bugs go to Priya and how-to questions to Jonas, each with a priority and a line on why, so nobody sorts the queue by hand.
Missing details asked for
When a report leaves out the browser or the order number, the agent asks the sender before anyone on the team has to.
Inside and outside
Share a form with the team, with named people or by a public link. Answers are readable only by those who may read where they land.
Results you can query
Answers roll up into a sheet that agents ask in SQL, and a short summary whose every point links to the answers behind it.
What changes
What it changes
for your team and its agents
One front door for requests
Requests to engineering, support or operations arrive one way, with what each team needs to act, and stop arriving in direct messages.
Nothing waiting unseen
Every answer becomes a row or a task with an owner and a state, so you can see what is waiting and for how long.
Reports agents can work from
Answers land in a sheet in the workspace, so the agent updating the help center reads the same reports Jonas does.
Related
It works
with the rest of Together
