Support
Email a person. That is the whole system.
No ticket portal, no account to create, no bot triaging you first. Write to the address below and one of the people who builds this answers — within one business day, and never more than two.
Get in touch
Two ways, and neither needs an account.
Web form
If you would rather not use mail, the contact form reaches the same people. Say what is wrong in the message field.
Open the formOne business day to a reply, two at the outside.
Answered by a person who works on the product.
What to include
- Your Slack workspace or Teams organisation, and the channel or chat it happened in.
- Roughly when — a timestamp or a link to the message is ideal.
- What you asked the bot, and what it did instead.
- Whether it is happening for everyone or only for you.
Do not send us credentials, tokens or API keys. We never need them, and a support thread is not where a secret should live.
Not using it yet
Questions before you install are welcome at the same address. The install page covers the permissions and what happens after, and pricing covers the bill.
Common fixes
Most of what goes wrong, and what to do about it.
These are the ones support hears about most, roughly in order. None of them needs us — but write anyway if the answer here does not match what you are seeing.
I mentioned it and nothing happened.
Four causes, in the order to check them:
- It is not in the channel. Type
/invite @attest_tagthere. It can only see channels it was invited to. - It was not actually mentioned. Outside a DM it answers when addressed — unless an admin has switched a channel to answer without being mentioned.
- The channel has hit its budget. Budgets pause a channel rather than surprising you with a bill; an admin raises it in the console.
- Your account is outside the allowed email domain. Workspaces can restrict the app to their own domain, which leaves guests and Slack Connect members out — and in Microsoft Teams, guests and people from other organisations. An admin can see this. A new Microsoft 365 organisation’s addresses are often on
yourcompany.onmicrosoft.com, which has to be on the list too.
It says it cannot see a channel or a document.
That is the design, not a fault. It reads the channels it was invited to and the documents an admin scoped to that channel, and a search runs on behalf of the person asking — so it will never surface something you could not find yourself. If you need it somewhere new, invite it there; if a document should answer in more channels, an admin changes its scope in the console.
It stopped part-way through, or said it ran out of rounds.
A single request gets a fixed number of tool rounds and a channel gets a budget, both so a loop cannot run up a bill unnoticed. When it reaches either it stops and says so, with what it found so far. Ask a narrower question, or have an admin raise the ceiling for that channel.
It asked me to confirm something and I closed the thread.
Nothing happened — that is the point of the card. A held write expires on its own if nobody presses anything, and no change is made in the connected service. Ask again and a fresh card appears. If a write needs an approver rather than you, it goes to them by DM.
The answer was wrong.
Send us the thread link. Model output is assistive and can be wrong, which is why every reply names what it read and every write waits for a person — but a wrong answer with a source attached is usually a scoping problem we can fix, whether that is a stale document, a channel that needs different instructions, or a model that is too small for the job.
How do I get it out of one channel — or out of the workspace?
One channel: remove the channel in the console and the app leaves it, or type /kick @attest_tag in Slack. Its access to that conversation ends immediately either way.
The whole workspace: a Slack admin removes the app under Manage apps in the workspace settings. Every token Slack issued is revoked at that moment. Ask us and the organisation’s stored data goes too.
In Microsoft Teams: remove it from the team to take it out of that team’s channels. For the whole organisation, an admin disconnects it under Workspaces in the console, after which the bot answers nothing there but how to connect it again; a Teams admin can also block the app in the Teams admin centre. Its record of your Teams conversations is part of the organisation’s stored data.
Can it post as someone, or read a channel it is not in?
No to both, and neither is a setting. It posts only as itself — an admin can give a channel its own name and icon for the app’s own messages, which Slack still marks as an app. It has no scope that reads a conversation it was not added to. Every permission it asks for is listed with its reason.
Where is the admin console?
At your own deployment, not on this site — sign in here and it will take you to it. If you do not have an account, ask whoever installed the app to invite you; an invitation is bound to the one address it was sent to.
For admins
Most answers are a setting, not a ticket.
Whoever installed the app can change nearly everything a user runs into, from the console.
Per-channel settings
Instructions, model, budget and connections are set per channel. Nothing is workspace-wide until you attach it to the workspace.
Connections
Add a service, test the credential before saving it, or send a setup link to whoever holds the token.
Audit and budgets
Every run is recorded with what it read, what it cost, and who confirmed the writes.
Installing it
The install flow end to end, in Slack and in Microsoft Teams: the consent screen or the upload, the invite, and what happens after.
Security & privacy
Reporting something, or asking for your data.
A vulnerability
Mail [email protected] with “Security” in the subject. Our vulnerability disclosure policy sets out the scope, the safe harbour for good-faith research, and the windows we hold ourselves to — worth two minutes before you start.
Access, export or deletion
Write from the address on the account and say which organisation. What we hold, how long we hold it, and who processes it are set out in the privacy policy, the DPA and the subprocessor list.
Removing the app from your Slack workspace revokes its access at once, and disconnecting a Teams organisation in the console stops it answering there — you do not need us for either, and it is the right first move if you think something is wrong.
Still stuck? Write to us.
[email protected] reaches the people who build this. One business day, no account, no portal.