Day-to-day agents

Agents is at /crm/agents, and the Agents button in the CRM header opens it. It holds two tools: the QR generator and Meeting digests.

QR generator

Make a QR for any link, and keep it to open again later.

1. Open /crm/agents and choose QR generator.
2. Give the QR a Name so you can tell your QRs apart. The name is not part of the link.
3. Enter the Base URL. It defaults to https://fireai.in/get-demo but can be any http or https link.
4. Add the Parameters you want on the end of the link: a parameter name and its value, as many as you need, for example utm_source = expo-2026. Parameter names cannot contain spaces and each can be used once.
5. Press Generate QR, then copy the link or download the QR as a PNG.

Every QR you generate is saved and listed under the form. Click one to open it again with its parameters. You only see the QRs you made.

For fireai.in links with a utm_source, the list shows how many leads each QR has brought in. A lead is counted when it is created with that utm_source.

Meeting digests

Summarise recorded meetings, such as the sales, client delivery, tech and marketing standups, and email the summary to the team owner and anyone else on a schedule. A digest can also review each stakeholder who runs those meetings and compare who is running them properly and asking the right questions. The owner can turn a summary into a pre-read for a stakeholder call.

Add the AI key

The AI key writes the summaries, the per-stakeholder reviews and pre-reads for every digest in the workspace.

1. Open /crm/agents and choose Meeting digests.
2. Under AI model, press Add AI key.
3. Paste the API key, then pick the Provider and Model from the lists: Google Gemini (gemini-3.5-flash, gemini-3.5-flash-lite, gemini-3.1-flash-lite), OpenAI (gpt-4.1-mini, gpt-4.1, gpt-4o-mini, gpt-4o), Anthropic (Claude) (claude-opus-5-5, claude-sonnet-5-5, claude-haiku-5-5) or OpenRouter (openai/gpt-4.1-mini, google/gemini-3.5-flash, deepseek/deepseek-chat, meta-llama/llama-3.3-70b-instruct). Pasting a Google, OpenAI, Anthropic (sk-ant-…) or OpenRouter key picks that provider for you. Checking a Claude key makes one tiny request, so an Anthropic account without credit is caught before the key is saved. For anything else, choose Custom base URL… or Custom model… and type it; any OpenAI-compatible provider with an https base URL works.
4. Press Check and save. The key is tested with a small request to the provider first. A key the provider rejects, or a model it does not offer, is not saved and the reason is shown. If the provider is rate limiting or down, the key is saved as Not checked; press Check later.

If your server already has an AI key (CRM_DIGEST_AI_KEY), the panel shows Server key and digests use it without adding anything here. Google AI keys go to Gemini (gemini-3.5-flash) and other keys to OpenAI, unless the server also sets CRM_DIGEST_AI_MODEL or CRM_DIGEST_AI_BASE_URL. A key saved on this page takes priority over the server key; remove it to go back to the server key. Only CRM admins, owners and leads can replace a server key. When you paste a Google AI key, the model and base URL switch to Gemini's.

The key is stored encrypted and is never shown again; the page shows only its last four characters. Press Change to switch the model or base URL without pasting the key again, or to replace the key. Anyone can add the first key. After that, only CRM admins, owners and leads, or whoever added it, can change or remove it. If the provider later rejects the key, it is marked Invalid and digests fall back to Fathom's own summaries until it is fixed.

Add Fathom keys

1. Open /crm/agents and choose Meeting digests.
2. Under Fathom keys, add one key per stakeholder who runs standups and calls. Name it after the stakeholder, such as Sales – Asha, Delivery – Ravi or Tech – Dev, paste the API key of that person's Fathom account (Fathom → Settings → API Access), and press Add and check. Add as many keys as you have stakeholders.
3. The key is checked with Fathom before it is saved. A key Fathom rejects is not saved, and the reason is shown. The same key, or a name already in use, cannot be added twice.
4. Each saved key shows Valid, Invalid or Not checked. Not checked means Fathom could not be reached or was rate limiting when the key was added; press Check to try again. Press Check at any time to test a key again. A key that stops working is marked Invalid with the reason under its name. A Fathom outage does not mark a key invalid.

A key only sees the meetings that Fathom user can open. Keys teammates connected in CRM Settings → Fathom are listed too, and can be used in a digest. Remove those from CRM Settings, not here.

You see the keys you added and your own CRM Settings key. CRM admins, owners and team leads see every key.

Make a digest

1. Press New digest. To fill in the name, keywords and prompt for a common standup, pick a starting point: Sales standup, Client delivery, Tech standup or Marketing standup.

2. Pick the Fathom keys to read.

3. Choose the Title keywords. Once keys are picked, Suggested from Fathom offers the titles of the meetings those keys recorded in the last 30 days, one option per recurring meeting, with how many times it happened. Hover an option to see which stakeholders ran it. The meetings that happened more than once are shown first; press Show all for the rest. Use Search or add a keyword to find a specific title, or to add your own keyword: type it, for example standup, and press Enter or Add “standup” as a keyword. It shows how many of the listed meetings it matches. Dates, times and numbers are left out of the titles, so Sales standup – 28 Oct and Sales standup – 29 Oct show as one option, Sales standup. Click an option to add or remove it. For a new digest, the meetings that happened more than once are filled in for you until you change the keywords yourself. You can also type keywords, separated by commas. A meeting is included when its title contains any keyword, ignoring case. Leave it empty to include every meeting the keys can see.

4. Check the Prompt: what the summary should cover. A new digest starts with a standup prompt that asks for what each standup covered; every question asked, who answered it and the answer, with unanswered questions marked; each person's major points (what they finished, what is next, blockers, help asked for); each stakeholder's decisions, action items with owner and date, and blockers left without an owner; and the top highlights for the team owner. Edit it to fit, or leave it empty to use the same standup prompt.

5. Enter the emails to Send to, separated by commas. Your email is filled in to start.

6. Choose the schedule. Each one summarises its own period:

   • Every weekday (Mon–Fri) is sent Monday to Friday and covers the day before. Monday's email covers Friday to Monday, so Friday's standups are not missed. This suits daily standups.
   • Every day is sent every day, weekends included, and covers the 24 hours before it.
   • Weekly covers the last 7 days and is sent on the day you pick.
   • Every 2 weeks covers the last 14 days and is sent on the day you pick, every other week.
   • Monthly covers the month before the send and is sent on the day of the month you pick, from 1 to 28.

   The time is in the timezone you pick from the list; it starts as your browser's timezone.

   Then choose What each email covers, separately from when it is sent: Since the previous email (the period above), the last 24 hours, 7, 14 or 30 days, this week so far (from Monday), this month so far (from the 1st), or the whole previous month. For example, send every weekday but cover the week so far, or send on the 1st and cover the whole previous month. A line under the schedule says when the digest sends and which meetings each email covers.

7. To compare stakeholders, tick Review each stakeholder, or start from the Stakeholder review preset.

8. Under Preview, pick which meetings to summarise now: the same meetings as each email, the last 24 hours, 7, 14 or 30 days, this month so far, or custom dates (up to 92 days). This only filters the preview; the Email schedule decides what each email covers.

9. Press Preview summary to read this period's meetings and see the summary before anything is sent, then Save digest.

Untick Send on schedule to pause a digest without deleting it.

What the summary is written from

Summaries are written from each meeting's Fathom transcript, what people actually said, not from Fathom's own notes. The whole transcript is used: a typical 30-minute call goes in complete. If a period is so long that some transcripts have to be shortened, the preview says which ones; preview a shorter period to include them in full.

A meeting is included when it started inside the period. Meetings Fathom has not finished transcribing yet are listed in the preview as no transcript yet, not in the summary, and are left out until their transcript is ready.

Who asked and answered

Every summary lists the questions asked in each meeting, who asked them, who answered and what they said. These come from the Fathom transcript: an answer is the next person to speak after the question, and a question with no reply is marked Unanswered. Very short questions such as "Right?" are left out.

The preview and the email also show a Who asked and answered table: for each person, how many questions they asked, how many answers they gave, and how many of their questions went unanswered.

Review each stakeholder

With Review each stakeholder ticked, each meeting is credited to the stakeholder whose key recorded it. When several keys can see the same meeting, it goes to the person who recorded it and is counted once.

For each stakeholder the digest measures, from the Fathom transcripts:

• how many meetings they ran and for how long
• how many questions they asked, per meeting
• how much of the talking they did
• how many action items came out of the meetings, and how many have an owner

These numbers appear as a Stakeholder scorecard in the preview and at the top of the email.

When an AI key is added, each stakeholder's meetings are also summarised separately from their transcripts and judged on how they were run: stating the agenda, following up on last period's commitments, getting an update from everyone, asking probing questions, getting blockers an owner, and ending with owned and dated action items. Each review lists the questions the stakeholder should have asked and gives a score out of 10. A final summary then ranks the stakeholders and says who is running meetings well, who needs to improve and how, and the risks and decisions that need the manager.

Without an AI key, the digest shows the scorecard and each stakeholder's Fathom summaries, without judging the meetings.

Preview, send and pre-reads

• If you change the prompt, keywords, keys, stakeholder review or preview period after previewing, the summary shows The prompt changed since this summary was written (or The settings changed). Press Apply to rewrite it; a spinner covers the old summary until the new one is ready, and sending is paused meanwhile. A summary written with the current settings shows ✓ Written with the current prompt and settings.
• Preview summary lists the meetings it found, with their attendees and links to the recordings, and shows the summary. You can edit the summary, then press Send this to … to email your edited version.
• Under the summary, pick PDF or Word (.docx). Download saves the summary as that file, with the stakeholder scorecard and links to the recordings. Send test email to me emails the summary, as currently written, only to you with the file attached, so you can check how it looks before it goes to anyone else. A test email is not counted as a sent digest. The file is stored privately and the link the email uses expires after an hour. If the file cannot be stored, the test email arrives without it and the page says why; use Download instead.
• Send now collects and sends a fresh summary straight away.
• Sent lists every digest that went out, on schedule or by hand. Press Open to read one again.
• Draft pre-read from this summary turns the summary into a pre-read for a stakeholder call. Add a note about who the call is with to focus it.

If a key stops working, the digest still goes out with the other keys' meetings, and the problem is shown on the sent entry and on the key.

How summaries are written

When an AI key is added under AI model, the summary follows your prompt and is written from each meeting's transcript, Fathom summary and action items. Without one, the digest puts together each meeting's own Fathom summary and action items, and the prompt and pre-reads are not used. The page says which applies.