SwiftFox AI
Limitations & best practice

SwiftFox AI — Limitations & best practice

Manage SwiftFox permissions, avoid limits, and get accurate record handling.

September 18, 2026
ID:
439

SwiftFox AI is genuinely useful for everyday work, and it is also still developing. This guide covers what it can and cannot do today, and the habits that get better answers out of it.

SwiftFox AI is in active development

The foot of every SwiftFox AI screen reads SwiftFox AI is in active development. It may get things wrong.

Take that at face value. Treat what SwiftFox AI tells you the way you would treat a colleague's summary: useful, usually right, worth checking before you act on anything consequential — sending a campaign, changing a record, or reporting a number to someone else.

Answers do not carry links to the help material they were drawn from, so verifying means checking the product or the user guides yourself.

Its knowledge of SwiftFox improves regularly. A question that gave a thin answer a few weeks ago is worth asking again.

What it can see

  • Your records, within your permissions. SwiftFox AI cannot see or change anything you could not see or change yourself. Two colleagues asking the same question can get different results.
  • Records you attach, and the record on the page you are on. See Giving SwiftFox AI the right context.
  • Images you give it — an attached image, or a screen capture.

Access to SwiftFox AI itself is controlled by the SwiftFox AI Agent permission in a user group. See SwiftFox AI — Overview.

Current limitations

  • Conversations cannot be renamed or deleted. SwiftFox AI names each one for you and it stays in your history.
  • Searching your chats matches titles, not message content.
  • @ tagging finds people only. Use Add to chat for organisations, lists, emails and events.
  • Screen capture is not offered on the SwiftFox AI page, only in the drawer and from the Home page prompt bar.
  • Reloading your browser starts a new conversation, though the previous one is kept in your history.

Getting better answers

Attach the record instead of describing it. This is the single biggest difference. Accuracy is largely a function of how precisely you have identified what you are talking about — if a request depends on a specific person, list, event or email, attach it rather than naming it in a sentence.

Check what has been attached for you. On a record page, that record is attached automatically and labelled From page. Glance at the chips above the composer before you ask, and remove anything irrelevant.

Show it rather than describing it. When you are stuck and do not have the vocabulary for the problem, a screen capture and why can't I send this will often get further than a paragraph of description.

Start a new chat when the subject changes. A conversation carries its attached records and its history forward, which helps while you stay on one subject and muddies things when you do not.

Ask follow-up questions. SwiftFox AI keeps track of what you are working on, so refining a list or a draft in the same conversation works better than starting over with a longer request.

Use the feedback controls

Under each answer are copy, Upvote and Downvote controls. The votes are how answer quality is measured and improved — a downvote on a wrong answer is more useful than rephrasing the question and moving on.