Questions people ask before they start

A workspace where your team uploads what it knows, builds an AI agent for each job, and turns the work that repeats into workflows.

On iOS, Android and the web. The same workspace, agents and documents on all three.

With Google or Apple, or with a one-time code sent to your email. There's no password to remember. The first time you sign in, tting creates a personal workspace for you.

English and Korean. It follows your device language and defaults to English.

No. Every workspace comes with a tting agent that explains what you can do and takes you to the right screen. Upload a document and ask about it, or install an agent from the marketplace.

An AI teammate for one job. It has a name, a description, instructions, a model, the skills it follows, the Knowledge it may read, the connectors it may use and an approval policy. Everyone in the workspace can use it.

A new version is created. Conversations already running finish on the version they started with. You can roll back to an earlier version.

Yes. Switch from the conversation header and the same thread continues with the other agent.

Claude, GPT, Qwen and Kimi, on every plan. Each agent has a default and you can change it per conversation. All of them run on Amazon Bedrock.

Yes, automatically when it helps. There's no per-agent switch. Web sources are cited with the same numbers as your own documents.

You can dictate. Click or tap the mic in the message box and your device or browser turns your speech into text. Your voice isn't sent to tting.

No. Only the person who started a conversation sees it.

The agent new conversations and new members start with. Every workspace has one. Admins can make any agent the representative.

No. They are maintained by tting and present in every workspace. To customize, build your own agent and make it the representative.

Ask the AI, call an agent, check a condition, send a notification and save a file, in the order you set. It starts on a schedule or on request.

Not yet. The five step types cover the work without code.

A failed run always notifies the people listed on the workflow. Success notifications can be turned on too. The run history stays with the workflow for as long as your plan keeps it.

Knowledge is what agents answer from, with the source shown. A reference is a file a workflow reads directly each time it runs, up to 10 per workflow.

Notion, plus Google Drive, Calendar, Docs, Sheets, Slides, Gmail and Contacts. Each member connects with their own account. When you ask, agents can create and edit Notion pages, Google Docs, Sheets and Slides files, and calendar events. By default this runs without asking. Gmail only reads and creates labels, and Contacts uses only your basic profile. You can also add your own connector by server URL.

Not yet. Agents can draft the message for you to send yourself.

No. tting doesn't train models on your content. Answers are generated on Amazon Bedrock, not on the model makers' own servers, so what you type isn't used to train their models. A few other services handle specific jobs, like document search, text extraction from uploads and web search. The Privacy Policy lists them all.

In Amazon Web Services data centers in Ireland. Files are encrypted at rest. AI answers are generated on Amazon Bedrock in London, and GPT and Kimi requests may be processed in other AWS regions.

tting staff can see file names and sizes, never what's inside. Conversation text is opened only for a support case with your consent, and every such access is logged.

Yes, unless an agent or workflow still uses it. tting shows you which ones so you can detach it first. Deleting is final; there's no trash yet.

From Settings, or through the account deletion page. If you own a company workspace, delete that workspace or transfer its ownership before you delete your account.

Everyone gets a personal workspace on sign-up; it is always one person. A company workspace is for a team: invite by email, with owner, admin and member roles. The two do not share data.

A flat monthly price for personal plans and a per-user price for company plans, plus points for model usage. See pricing.

The unit model usage is charged in. 1,000 points is one dollar. Paid plans include points every month and you can top up any time.

Paid sales by marketplace sellers (they open when seller payouts launch), sending email or posting to Slack, two-way voice conversations, file version history, folders and a trash in Storage, and code steps in workflows. All of these are planned for later versions.