Talavine
Talavine is built by a small team and it's still preview-stage software, so we'd rather tell you exactly what to expect than promise a support desk we don't have. There's no phone number and no 24/7 coverage. There is a real person reading support@swarmmarshal.com, a bug button inside the app that does most of the diagnostic work for you, and the guides below.
Write to support@swarmmarshal.com for anything specific to you: a hosted CRM tenant (including closing one), a billing question, an account you can't get connected, or a problem you'd rather not describe in public.
We read every message. We can't promise a response time (we're a small team, not a support organization), but nothing goes into a void.
The community board is the public place for setup questions, workflow ideas, feature requests, and "is anyone else seeing this?" Answers there help the next person with the same question, which email never does.
The board is public, so don't post logs, message contents, API keys, or anything else you wouldn't want indexed. Send those to support instead.
Look at the status bar along the bottom of the Talavine window and click the bug icon. The app asks you to confirm, then sends a report that already includes your app version, a screenshot of what you were looking at, and the tail of your local diagnostics log.
It sends from one of your own connected email accounts, so the report lands in your Sent folder and you can read exactly what left your machine. If you haven't connected a mail account yet, the button will tell you so; email support@swarmmarshal.com instead.
Things that work but annoy you (a label that reads badly, a workflow that takes four clicks, a model that keeps guessing wrong) are worth telling us about too, and the community board is the better home for those. It gives other people a chance to say "yes, that one" and helps us rank them honestly.
If you think you've found a security issue in the desktop app, this website, the MCP server, the local data stores, or credential handling, report it privately to security@swarmmarshal.com rather than posting it on the community board or in a public issue.
Please include:
You'll get an acknowledgement within seven days, and a remediation plan within thirty days for confirmed issues. Please do not include real personal data, real API keys, or live credentials in a report. If a reproduction needs sensitive material, ask first and we'll arrange a safer channel.
Most first-run trouble is OAuth, not Talavine. Outlook signs in with one click, and its guide shows what to send IT when an organization requires approval. The Google guide walks through creating your Google app step by step. Both end with a troubleshooting section covering the exact error codes Google and Microsoft return.
If nothing is broken yet and you're just trying to get going, start with the setup guide and the FAQ. Between them, they cover most of what people email us about in the first week.
The in-app bug button collects most of this automatically. If you're writing to us by email instead, these five lines are the difference between a fix and a round of questions:
Your data stays on your machine, so we can't look at your mailbox to reproduce a problem. The details you send us are all we have to go on. Please redact anything private before you attach it.
support@swarmmarshal.com for anything private or account-specific. The community board for anything the next person would also want the answer to.