Beta

Claims and suggestions

Every claim answered, none lost

A QR code on the counter, a link on your website or on a receipt. Each claim becomes a task with an owner, and the customer can see where it stands.

Start with the claims example All use cases

The example comes ready: a form, the claims it brought in, and a team answering them.

From the counter to the right person

A form of your own, a QR code to print

You write the questions: short or long text, choices, dates, an email address, yes or no, file uploads. The page shows your logo and your name. Download its QR code as an image for a poster, a counter card or a receipt; the link works the same in an email or on your website.

A QR code, the form it opens, and the request on its way to the team

Each claim is a task

Owned, prioritised, never forgotten

A claim lands in the project you choose, assigned to a person or waiting for a team member to take it. Priorities, due dates, comments and history work as for any task.

A queue of requests stacked by priority, each with its owner

The sender is kept informed

Switch it on and the sender gets an email when the status or the priority of their request changes, and the comments your team chooses to send them. Each email links to a page where they follow the request by its number and their email address, and can answer the team.

Nothing else leaves your workspace: not the assignee, the description, the files or the team's other comments.

A daily limit

A flood of spam costs you a number, not a full project.

A robot check

Optional, before a request can be sent.

Your languages

A version of the form in each language you serve.

How public forms work

Try it with the example

Your workspace starts with the form, five requests in different states, and the team answering them. Remove it with one click when you are done.

Start with the claims example