49 min readAmbient capture

Implementation Guide: Transcribe client onboarding calls and generate engagement letter drafts

Step-by-step implementation guide for deploying AI to transcribe client onboarding calls and generate engagement letter drafts for Accounting & Bookkeeping clients.

Hardware Procurement

Jabra Speak2 75 USB/Bluetooth Speakerphone

Jabra (GN Audio)2775-419 (Microsoft Teams variant) / 2775-109 (UC variant)Qty: 1

$250–$280 MSP cost / $350–$400 suggested resale

Primary conference room speakerphone for group onboarding meetings. Features 4 noise-cancelling beamforming microphones, super-wideband audio, and 360° pickup optimized for 4–8 person rooms. Provides the high-fidelity audio capture essential for accurate transcription of multi-speaker onboarding calls.

Jabra Speak2 55 USB/Bluetooth Speakerphone

Jabra (GN Audio)2755-419 (Microsoft Teams variant) / 2755-109 (UC variant)Qty: 3

$120–$130 MSP cost / $175–$200 suggested resale per unit

Individual office speakerphones for 1-on-1 onboarding calls conducted from partner or manager offices. 4 beamforming microphones with full-duplex audio and echo cancellation eliminate the hollow tunnel sound common with laptop microphones, ensuring clean transcription capture for desk-based calls.

USB-A to USB-C Adapter Cables

Anker / Cable MattersAnker A8153 or Cable Matters 201048Qty: 4

$8–$12 MSP cost / bundled with speakerphones

Ensures speakerphone compatibility with both USB-A and USB-C ports on firm laptops and desktops. Include one per speakerphone for deployment flexibility.

Software Procurement

Fireflies.ai Business Plan

Fireflies.aiBusiness PlanQty: per user

$19/user/month (annual) or $29/user/month (monthly) — typical 5-user firm = $95–$145/month

Core AI transcription platform. Automatically joins Zoom, Teams, and Google Meet calls as a bot participant. Provides speaker diarization, searchable transcripts, AI-generated summaries, and action items. Business tier includes unlimited transcription storage, conversation intelligence analytics, CRM integrations, and API access needed for the downstream engagement letter pipeline.

OpenAI API (GPT-5.4)

OpenAIGPT-5.4Qty: Usage-based API (pay-per-token)

$5–$15/month for typical accounting firm volume (20–40 calls/month). Input: $2.50/1M tokens, Output: $10.00/1M tokens. A single engagement letter generation costs ~$0.02–$0.05.

Large language model API used to process transcription summaries and generate structured engagement letter drafts. GPT-5.4 provides the nuanced professional language quality required for legal engagement documents while remaining cost-effective at accounting firm volumes.

Make.com (formerly Integromat) Pro Plan

Make (Celonis)SaaS monthly subscriptionQty: 10,000 operations/month

$16/month

Integration middleware that orchestrates the end-to-end workflow: receives webhook from Fireflies.ai when transcription completes → sends transcript to OpenAI API for engagement letter generation → routes the draft to the practice management system and/or document management platform. 13x more operations per dollar than Zapier at comparable pricing. Sufficient for 40+ calls/month with multi-step automations.

Ignition (formerly Practice Ignition) — Starter or Pro Plan

IgnitionSaaS monthly subscriptionQty: 1 user (Starter); team (Pro)

Starter: $49/month (1 user); Pro: $229/month (billed annually) or $279/month (monthly). Includes e-signature, automated billing, and engagement letter templates.

Accounting-specific engagement letter and proposal platform. Receives AI-generated draft data via API/Zapier and populates professional engagement letter templates with e-signature capability. Integrates natively with Xero and QuickBooks Online for automated billing tied to signed engagements. If the firm already uses GoProposal, Knuula, or Cone, substitute accordingly.

SmartVault Business Plan

SmartVaultBusiness PlanQty: per user/month

$20–$40/user/month depending on tier; typical firm = $100–$200/month

SOC 2 Type II certified document management platform purpose-built for accounting firms. Stores signed engagement letters, call recordings (if retained), and transcripts in a compliant, client-accessible portal. Provides the secure document repository required by GLBA Safeguards Rule. Skip if firm already uses ShareFile, Canopy Documents, or equivalent.

Fireflies.ai API Add-on

Fireflies.aiIncluded with Business plan API access

Included in Business subscription — no additional cost

Programmatic access to completed transcripts, summaries, and speaker-labeled segments. The Make.com webhook integration uses this API to automatically trigger the engagement letter generation workflow when a transcription is finalized.

Prerequisites

  • Active Zoom (5.x+), Microsoft Teams, or Google Meet subscription with admin-level access to authorize Fireflies.ai bot integration
  • Microsoft 365 or Google Workspace email accounts for all staff who conduct onboarding calls
  • Reliable internet connectivity: minimum 5 Mbps upload/download per concurrent call; 10 Mbps recommended. Wired Ethernet preferred in conference rooms.
  • Firewall/proxy configured to allow outbound HTTPS (port 443) to: *.fireflies.ai, api.openai.com, *.make.com, *.ignitionapp.com, and *.smartvault.com
  • Existing practice management system (Karbon, TaxDome, Canopy, or equivalent) with API access or Zapier integration capability
  • Written Information Security Plan (WISP) on file — will be updated during implementation to address AI transcription tools
  • Firm principal/partner authorization to implement AI transcription, including willingness to update engagement letter templates with recording consent and IRS Section 7216 consent language
  • Inventory of states where clients are located to determine one-party vs. all-party recording consent requirements (all-party consent states: CA, CT, DE, FL, IL, MD, MA, MT, NV, NH, PA, WA, DC)
  • Admin credentials for the firm's practice management system, document management system, and accounting software (QuickBooks Online, Xero) for integration configuration
  • At least one partner or manager designated as the 'AI Champion' who will review and approve engagement letter drafts during the pilot phase

Installation Steps

Step 1: Deploy Speakerphone Hardware

Physically install and configure USB speakerphones in all rooms where client onboarding calls will be conducted. The Jabra Speak2 75 goes in the primary conference room; Jabra Speak2 55 units go in individual partner/manager offices. Connect via USB to the room's primary computer or docking station. Pair via Bluetooth to the partner's laptop as a secondary connection option for mobile use.

1
Verify speakerphone is recognized by the OS (Windows)
2
Verify speakerphone is recognized by the OS (macOS)
3
Set as default audio device in Windows: Control Panel → Sound → set Jabra Speak2 as default Playback and Recording device
4
Install Jabra Direct for firmware updates and device management — download from https://www.jabra.com/software-and-services/jabra-direct
Verify speakerphone is recognized by the OS (Windows)
powershell
Get-PnpDevice -FriendlyName '*Jabra*' | Format-Table Status, FriendlyName
Verify speakerphone is recognized by the OS (macOS)
bash
system_profiler SPUSBDataType | grep -A 5 'Jabra'
Note

Run a 30-second test recording in Voice Recorder (Windows) or QuickTime (macOS) from each speakerphone position. Play back and verify: clear voice capture, minimal echo, no distortion. If the conference room has significant echo, consider adding acoustic panels. Ensure Jabra Direct firmware is updated to latest version before proceeding.

Step 2: Create and Configure Fireflies.ai Business Accounts

Set up the Fireflies.ai organization account with Business-tier licenses for all partners and managers who conduct onboarding calls. Configure SSO if available, set organization-level privacy defaults, and connect to the firm's video conferencing platform.

1
Navigate to https://app.fireflies.ai/signup and create organization admin account
2
Go to Settings → Billing → upgrade to Business plan
3
Invite team members via Settings → Team → Invite Members
4
Configure integrations: Settings → Integrations → Connect Zoom (OAuth) / Microsoft Teams / Google Meet
5
Set organization defaults: Settings → Privacy → set 'Auto-join meetings' to 'Only meetings I organize' initially | Settings → Privacy → enable 'Notify participants when Fireflies joins'
6
Configure custom vocabulary: Settings → Custom Vocabulary → add accounting terms
Custom vocabulary terms to add under Settings → Custom Vocabulary
text
1040, 1065, 1120-S, S-Corp, C-Corp, LLC, GAAP, GAAS, QBO, W-2, W-9,
990, 501(c)(3), basis, depreciation, amortization, accrual, cash-basis,
engagement letter, retainer, tax preparation, bookkeeping, advisory
Critical

Set auto-join to 'Only meetings I organize' during initial setup to prevent Fireflies from joining internal meetings or non-onboarding calls. Expand to 'All meetings' only after staff training. Ensure the 'Notify participants' setting is ALWAYS enabled — this is required for recording consent compliance in all jurisdictions. Custom vocabulary significantly improves transcription accuracy for accounting-specific terms like entity types and form numbers.

Implement a multi-layered consent system that satisfies state recording laws, AICPA confidentiality rules, and IRS Section 7216 requirements. This includes written consent in the engagement letter, a verbal disclosure script read at the start of each call, and automated notification from Fireflies.ai.

1
No CLI commands — this step involves document and process creation
2
Create the following documents and store in the firm's document management system

Document 1: Verbal Disclosure Script

To be read at the start of every onboarding call. Save as: /templates/verbal-recording-disclosure.docx

Verbal Recording Disclosure Script
text
# read verbatim at the start of each onboarding call

Before we begin, I want to let you know that we use an AI-powered
transcription service to record and transcribe our meetings. This helps us
accurately capture your information and generate your engagement documents
more efficiently. The recording and transcript are stored securely and are
subject to the same confidentiality protections as all your financial
information. Are you comfortable proceeding with the recording? If not,
I am happy to take notes manually instead.

Save as: /templates/ai-transcription-consent-addendum.docx. Must include IRS Section 7216 consent language per Rev. Proc. 2013-14.

Document 3: Updated Engagement Letter Template

Add an AI disclosure paragraph to all engagement letter templates in Ignition/GoProposal.

Note

LEGAL REVIEW REQUIRED: Have the firm's legal counsel or a compliance-focused CPA review all consent language before deployment. IRS Section 7216 consent forms have SPECIFIC required language elements — do not improvise. For clients in all-party consent states (CA, CT, DE, FL, IL, MD, MA, MT, NV, NH, PA, WA, DC), the verbal disclosure is legally mandatory. Build an opt-out workflow: if a client declines recording, the partner takes manual notes and the engagement letter is created through the traditional process.

Step 4: Set Up OpenAI API Access

Create an OpenAI organization account, generate an API key for the engagement letter generation pipeline, configure usage limits to prevent runaway costs, and test the API connection.

1
Navigate to https://platform.openai.com/signup
2
Create organization: Settings → Organization → set name to '[FirmName]-AI-Pipeline'
3
Add payment method: Settings → Billing → Add payment method
4
Set usage limits: Settings → Billing → Usage limits - Set monthly hard limit: $50 (sufficient for ~1,000 engagement letters) - Set email alert at: $25
5
Generate API key: API Keys → Create new secret key - Name: 'engagement-letter-make-integration' - Permissions: 'Chat completions only' (principle of least privilege)
6
Test the API key:
Expected response: {"choices": [{"message": {"content": "OK"}}]}
bash
curl https://api.openai.com/v1/chat/completions -H 'Content-Type: application/json' -H 'Authorization: Bearer sk-YOUR_API_KEY' -d '{"model": "gpt-5.4", "messages": [{"role": "user", "content": "Respond with OK if you can read this."}], "max_tokens": 10}'
Note

SECURITY: Store the API key in Make.com's encrypted connection settings — never in plaintext in scenario configurations. The $50/month hard limit is a safety net; actual costs for 20–40 engagement letters/month will be $5–$15. If the firm processes sensitive tax data through the API, verify that OpenAI's data usage policy (https://openai.com/policies/api-data-usage-policies) confirms API data is NOT used for training. As of 2024, OpenAI confirms API data is not used for model training by default.

Step 5: Build the Make.com Automation Workflow

Create the core automation scenario in Make.com that orchestrates the full pipeline: Fireflies.ai transcript completion → data extraction → GPT-5.4 engagement letter generation → output routing to practice management and document management systems. This is the central nervous system of the solution.

1
Module 1: Webhook — Fireflies.ai Transcript Ready — Trigger: Fireflies webhook sends POST when transcription completes. URL: https://hook.us1.make.com/[your-unique-webhook-id]. Payload includes: transcript_id, meeting_title, participants, transcript_text, summary.
2
Module 2: HTTP — Fetch Full Transcript from Fireflies API — Method: POST to https://api.fireflies.ai/graphql. Headers: Authorization: Bearer [fireflies_api_key]. Body: GraphQL query for transcript with speaker labels.
3
Module 3: OpenAI — Generate Engagement Letter Draft — Connection: OpenAI (API key from Step 4). Model: gpt-5.4. System prompt: [See custom_ai_components section for full prompt]. User message: Transcript summary + full transcript. Max tokens: 4000. Temperature: 0.3 (low creativity for professional documents).
4
Module 4: Router — Branch based on service type detected. Route A: Tax preparation engagement → tax template. Route B: Bookkeeping engagement → bookkeeping template. Route C: Advisory/consulting engagement → advisory template. Route D: Audit/review engagement → audit template.
5
Module 5: HTTP — Create draft in Ignition (or practice management system). Method: POST to Ignition API or push to Karbon via API. Alternatively: Create Google Doc / Word doc in shared drive.
6
Module 6: Email — Notify partner/manager that draft is ready for review. To: meeting organizer email. Subject: '[AI Draft Ready] Engagement Letter — {{client_name}}'. Body: Link to draft document, summary of extracted terms.
7
Module 7: Google Sheets / Airtable — Log the transaction. Record: date, client name, service type, partner, status.
Fireflies GraphQL query for transcript with speaker labels (Module 2)
graphql
{ transcript(id: "{{1.transcript_id}}") { sentences { text speaker_name } summary { action_items overview } } }
  • Add error handler to Module 3 (OpenAI): retry 2x with 30-second delay.
  • Add error handler to Module 5: if API fails, email draft as attachment instead.
  • Add a global error notification email to MSP support.
Note

Start with a simplified 3-module scenario (Webhook → OpenAI → Email notification) during testing phase. Add the routing, practice management integration, and logging modules after the core pipeline is validated. Make.com's visual scenario builder makes this accessible to Tier 2 MSP technicians. Save the complete scenario as a template for reuse across accounting firm clients. The GraphQL query for Fireflies may need adjustment based on their current API schema — check https://docs.fireflies.ai for the latest.

Step 6: Configure Fireflies.ai Webhook to Make.com

Connect Fireflies.ai to the Make.com scenario so that completed transcriptions automatically trigger the engagement letter generation pipeline. This eliminates any manual export or copy-paste steps.

In Fireflies.ai

1
Go to Settings → Integrations → Webhooks
2
Add new webhook: URL: https://hook.us1.make.com/[your-unique-webhook-id] (from Make.com Module 1)
3
Set Events to: 'Transcription Complete'
4
Set Filter (if available): Meeting title contains 'onboarding' OR 'new client'

In Make.com

1
Open your scenario
2
Click on the Webhook module → Copy webhook URL
3
Click 'Redetermine data structure' → trigger a test transcription in Fireflies
4
Make.com will capture the webhook payload structure automatically

Test the Connection

1
Start a test call in Zoom/Teams with Fireflies bot
2
Conduct a 2-minute mock onboarding conversation
3
Wait for Fireflies to complete transcription (typically 2–5 minutes)
4
Verify Make.com scenario triggers and processes correctly
Note

IMPORTANT: Add a meeting title filter so only onboarding calls trigger the pipeline. Without this, every recorded meeting (internal standups, vendor calls, etc.) will generate an engagement letter draft. Recommended naming convention: partners prefix onboarding meeting titles with 'Onboarding:' or 'New Client:' — the webhook filter catches these. Alternatively, create a dedicated Fireflies 'channel' for onboarding calls.

Step 7: Create Engagement Letter Templates in Ignition

Configure 4–5 engagement letter templates in Ignition (or the firm's engagement letter platform) that will receive data from the AI pipeline. Each template corresponds to a primary service type and contains merge fields for AI-generated content.

1
Go to Library → Templates → Create New Template in Ignition (https://app.ignitionapp.com)
2
Create templates for each service type: a. Tax Preparation — Individual (1040) b. Tax Preparation — Business (1065/1120-S/1120) c. Monthly Bookkeeping Services d. Advisory / Consulting Services e. Audit / Review / Compilation
3
For each template, add merge fields that map to AI output
4
Add the AI transcription consent clause to ALL templates
5
Add IRS Section 7216 consent language to all tax-related templates
6
Configure e-signature fields and routing rules
7
Connect Ignition to QuickBooks Online or Xero for automated billing
Merge fields to add to each template, mapping to AI pipeline output
text
{{client_name}}, {{client_entity_type}}, {{client_ein_or_ssn_last4}},
{{services_scope}}, {{fee_structure}}, {{fee_amount}}, {{billing_frequency}},
{{engagement_period}}, {{client_responsibilities}}, {{firm_responsibilities}},
{{deadline_dates}}, {{special_terms}}, {{ai_transcription_consent_clause}}
AI transcription consent clause — add to ALL templates
text
Client acknowledges and consents to the use of AI-powered transcription
technology during meetings and calls for the purpose of accurate record-keeping
and service delivery. All recordings and transcripts are maintained in accordance
with our firm's privacy policy and applicable professional standards.
Note

Work closely with the firm's managing partner to review and approve all template language. The AI pipeline will populate the merge fields but the templates contain the legal boilerplate that the firm's attorney has approved. If the firm uses GoProposal instead of Ignition, the same template structure applies — GoProposal has AICPA-aligned templates that may require less customization. If neither platform is in use, engagement letters can be generated as Word documents and stored in SmartVault/ShareFile for manual e-signature via DocuSign.

Step 8: Update the Firm's Written Information Security Plan (WISP)

Amend the firm's WISP to document the new AI transcription tools, data flows, vendor risk assessments, and security controls. This is required by the FTC Safeguards Rule (GLBA) and is a critical compliance step that cannot be skipped. ``` # No CLI commands — this step involves policy documentation # # Add the following sections to the firm's existing WISP document: # # SECTION: AI Transcription and Document Generation Tools # # 1. System Description: # - Fireflies.ai Business (transcription...

Step 9: Configure Data Retention and PII Handling

Set up appropriate data retention policies in Fireflies.ai and configure PII redaction where available. Ensure that call recordings, transcripts, and engagement letter drafts are retained only as long as needed and are protected throughout their lifecycle.

Fireflies.ai Data Retention Configuration

1
Settings → Privacy & Security → Data Retention: Set auto-delete for recordings: 90 days
2
Settings → Privacy & Security → Data Retention: Set auto-delete for transcripts: per firm policy (recommend 3 years)
3
Settings → Privacy & Security → Data Retention: Enable 'Delete recording after transcript is finalized' if recording storage is not needed long-term
4
Settings → Privacy & Security → PII Handling: Enable Smart Privacy features (if available on Business plan)
5
Settings → Privacy & Security → PII Handling: Configure PII redaction for: SSN patterns, EIN patterns, bank account numbers

OpenAI API Configuration

1
Verify data handling at https://platform.openai.com/docs/models — confirm: 'OpenAI does not use API inputs/outputs to train models'
2
In Make.com scenario, add a text processing module BEFORE the OpenAI call to redact PII using regex
Regex patterns for PII redaction in Make.com text processing module
regex
# Redact SSN patterns:
replace /(\d{3}-\d{2}-\d{4})/ with '[SSN REDACTED]'

# Redact EIN patterns:
replace /(\d{2}-\d{7})/ with '[EIN REDACTED]'

# Redact bank account numbers:
replace /(\d{8,17})/ with '[ACCT REDACTED]'

SmartVault / Document Storage

1
Set folder-level retention policies for engagement letter storage
2
Enable audit logging for document access
3
Configure client portal access permissions
Note

PII redaction before sending to OpenAI is a defense-in-depth measure. Even though OpenAI does not train on API data, minimizing PII exposure reduces risk. The regex-based redaction in Make.com is a lightweight first pass — it will not catch all PII but addresses the most common patterns (SSN, EIN). For firms with higher compliance requirements, consider AssemblyAI's built-in PII redaction feature as an alternative to Fireflies. Note: the engagement letter draft will need the actual client name and entity information — only redact highly sensitive identifiers like SSN/EIN from the LLM input.

Step 10: Pilot Testing with Live Onboarding Calls

Conduct 5–10 real onboarding calls using the full pipeline. Each call goes through the complete workflow: verbal consent → Fireflies recording → transcription → Make.com automation → GPT-5.4 engagement letter draft → partner review. Document quality issues and refine the system.

  • SCORING (1–5 scale): Accuracy of extracted information: ___
  • SCORING (1–5 scale): Completeness of engagement terms: ___
  • SCORING (1–5 scale): Professional tone and language quality: ___
  • SCORING (1–5 scale): Time saved vs. manual process: ___
Note

Expect the first 2–3 drafts to require significant editing. This is normal — use the feedback to refine the system prompt (see custom_ai_components). By draft 5–7, the system should produce engagement letters that require only minor partner edits. If transcription accuracy is poor for specific accounting terms, add more entries to Fireflies custom vocabulary. If a particular partner speaks very quickly or with an accent, run additional test calls to tune the system. Keep a shared spreadsheet of all pilot results for pattern analysis.

Step 11: Staff Training Session

Conduct a 2-hour training session for all firm staff who will interact with the system. Cover the technology workflow, consent procedures, draft review process, and troubleshooting common issues. Leave behind reference documentation.

1
Section 1: Overview (15 min) — What the system does and why; Privacy and compliance commitments; What AI can and cannot do (set expectations)
2
Section 2: Live Demo (30 min) — Conduct a mock onboarding call with the full pipeline; Show Fireflies dashboard: how to review transcripts; Show the engagement letter draft output; Show the review/edit/approve workflow
3
Section 3: Hands-On Practice (30 min) — Each partner/manager conducts a practice call; Review their own generated engagement letter draft; Practice editing and sending for e-signature
4
Section 4: Consent Procedures (20 min) — When and how to read the verbal disclosure; What to do if a client declines recording; Written consent in the engagement letter
5
Section 5: Troubleshooting (15 min) — Fireflies bot doesn't join: manual invite process; Poor audio quality: speakerphone positioning; Draft quality issues: flagging for MSP review; Emergency: how to delete a recording immediately
6
Section 6: Q&A (10 min)
Note

Record the training session (with staff consent) for future onboarding of new hires. Create a laminated quick-reference card for each office that covers: (1) Verbal disclosure script, (2) How to verify Fireflies is recording, (3) How to access and review engagement letter drafts, (4) Who to call if something goes wrong. Schedule a 30-minute follow-up session 2 weeks after go-live to address questions that arise from real-world usage.

Step 12: Go-Live and Monitoring Setup

Transition from pilot to production use. Enable the system for all onboarding calls, set up monitoring alerts, and establish the ongoing support cadence with the firm.

1
In Fireflies.ai: expand auto-join settings if desired → Settings → Auto-join → 'All external meetings' or keep at 'Organizer only'
2
In Make.com: enable scenario scheduling — Set scenario to 'On' (active), Set execution mode: 'Immediately' (webhook-triggered), Enable email notifications for failed executions → MSP support email
3
Set up monitoring: Make.com: Settings → Notifications → alert on any scenario error | OpenAI: Dashboard → Usage → verify daily spend is within expected range | Fireflies: Admin dashboard → check transcription volume weekly
4
Create a shared monitoring dashboard (use Google Sheets or Airtable) with columns: Date, Client Name, Call Duration, Transcript Quality (1-5), Draft Quality (1-5), Partner Edits Required, Time Saved (estimated) — this becomes the ROI report for the firm
5
Schedule recurring support: Week 1-2 post go-live: daily check-in (15 min email/call) | Week 3-4: twice weekly check-in | Month 2+: weekly or bi-weekly check-in | Ongoing: monthly metrics review and optimization call
Note

The first 2 weeks post go-live are critical. Be proactive — don't wait for the firm to report issues. Check the Make.com execution logs daily for the first week. Common early issues: (1) Fireflies bot not joining because meeting was created from a non-integrated calendar, (2) Webhook timing out because Fireflies takes longer than expected for long calls, (3) GPT-5.4 generating overly verbose engagement letters. All are easily fixable with configuration tweaks.

Custom AI Components

Onboarding Call Transcript Processor

Type: prompt System prompt for GPT-5.4 that processes a Fireflies.ai transcription of an accounting firm client onboarding call and extracts structured data needed for engagement letter generation. This prompt is used in the Make.com scenario (Module 3) and produces a JSON output that maps directly to engagement letter template merge fields. Implementation: ``` SYSTEM PROMPT: You are an expert engagement letter drafting assistant for a CPA / accounting firm. You will receive a transc...

Engagement Letter Draft Generator

Type: prompt Second-stage GPT-5.4 prompt that takes the structured JSON output from the Onboarding Call Transcript Processor and generates a professional, ready-to-review engagement letter draft. This produces the actual letter text that will be sent to Ignition or output as a Word document. Implementation: ``` SYSTEM PROMPT: You are a senior CPA firm engagement letter specialist. You will receive a structured JSON object containing extracted engagement details from a client onboardi...

Make.com Scenario: Onboarding-to-Engagement Pipeline

Type: workflow Complete Make.com automation scenario specification that connects Fireflies.ai transcript completion to the two-stage GPT-5.4 processing pipeline and routes the final engagement letter draft to the appropriate output destination. This is the central orchestration workflow. Implementation: ``` MAKE.COM SCENARIO SPECIFICATION ================================ Scenario Name: Onboarding Call → Engagement Letter Draft Scheduling: Instant (webhook-triggered) Max execution tim...

Custom Vocabulary List for Accounting Transcription

Type: skill Pre-built custom vocabulary configuration for Fireflies.ai that dramatically improves transcription accuracy for accounting-specific terminology. This vocabulary list covers tax forms, entity types, accounting standards, software names, and industry jargon commonly discussed in onboarding calls.

Implementation:

1
Navigate to: Settings → Custom Vocabulary → Add Terms
FIREFLIES.AI CUSTOM VOCABULARY LIST — TAX FORMS
text
TAX FORMS:
1040, 1040-SR, 1040-X, 1040-ES, 1065, 1120, 1120-S, 1120-H, 990, 990-EZ, 990-PF, 990-T, 941, 940, 944, 943, W-2, W-3, W-4, W-9, 1099-NEC, 1099-MISC, 1099-INT, 1099-DIV, 1099-B, 1099-R, 1099-K, 1099-S, 1099-G, 1098, 1098-T, K-1, Schedule C, Schedule E, Schedule K-1, Schedule SE, 8829, 4562, 2553, SS-4, 8832, 7004, 2290, 720
FIREFLIES.AI CUSTOM VOCABULARY LIST — ENTITY TYPES
text
ENTITY TYPES:
S-Corp, S-Corporation, C-Corp, C-Corporation, LLC, PLLC, LLP, sole proprietor, sole proprietorship, partnership, general partnership, limited partnership, 501(c)(3), 501c3, non-profit, nonprofit, disregarded entity, single-member LLC, multi-member LLC, professional corporation, P.C., SMLLC
FIREFLIES.AI CUSTOM VOCABULARY LIST
text
# ACCOUNTING STANDARDS & TERMS

ACCOUNTING STANDARDS & TERMS:
GAAP, GAAS, SSARS, accrual basis, cash basis, modified cash basis, accounts receivable, accounts payable, general ledger, chart of accounts, trial balance, adjusted trial balance, depreciation, amortization, Section 179, bonus depreciation, MACRS, straight-line, cost basis, fair market value, FMV, FIFO, LIFO, weighted average, bank reconciliation, journal entry, adjusting entry, closing entry, fiscal year, calendar year, engagement letter, management representation letter, compilation, review, audit, agreed-upon procedures, attestation
FIREFLIES.AI CUSTOM VOCABULARY LIST — TAX CONCEPTS
text
TAX CONCEPTS:
AGI, adjusted gross income, MAGI, modified adjusted gross income, standard deduction, itemized deductions, QBI, qualified business income, Section 199A, estimated payments, quarterly estimates, extension, tax extension, amended return, carryforward, carryback, NOL, net operating loss, capital gains, capital losses, wash sale, passive activity, material participation, hobby loss, home office deduction, self-employment tax, FICA, FUTA, SUTA, nexus, apportionment, multistate
FIREFLIES.AI CUSTOM VOCABULARY LIST — SOFTWARE & PLATFORMS
text
SOFTWARE & PLATFORMS:
QuickBooks, QuickBooks Online, QBO, QuickBooks Desktop, Xero, FreshBooks, Sage, Sage Intacct, Wave, Gusto, ADP, Paychex, Bill.com, BILL, Divvy, Expensify, Dext, Hubdoc, Receipt Bank, TSheets, Harvest, Karbon, TaxDome, Canopy, Drake, Lacerte, UltraTax, ProConnect, ProSeries, CCH Axcess, GoSystem
FIREFLIES.AI CUSTOM VOCABULARY LIST — INDUSTRY TERMS
text
INDUSTRY TERMS:
retainer, engagement, onboarding, offboarding, bookkeeping, write-up, bank feeds, categorization, reconciliation, month-end close, year-end close, 1099 filing, W-2 processing, payroll processing, quarterly review, annual review, tax planning session, tax projection, estimated tax payment, IRS, state revenue department, notice response, audit representation, power of attorney, Form 2848, CAF number
Note

CLIENT-SPECIFIC TERMS (update per client): Add firm name, partner names, proprietary service package names, and frequently referenced client names as they are identified during pilot testing.

Opt-Out Manual Workflow Fallback

Type: workflow

A documented manual workflow for situations where a client declines recording consent. Ensures the firm can still generate engagement letters efficiently without the AI pipeline, maintaining service consistency.

Implementation

TRIGGER: Client declines recording consent during verbal disclosure or in writing.

1
Partner/Manager acknowledges client preference: 'Absolutely, no problem at all. I will take notes manually during our conversation.' Do NOT start Fireflies recording. If auto-join is enabled, remove the Fireflies bot from the meeting.
2
Partner takes structured notes during the call using the provided 'Onboarding Call Notes Template' (Google Doc or Word template). Template mirrors the JSON structure from the AI pipeline.
3
After the call, partner completes the notes template — fill in any details from memory, then save to the client folder in practice management system.
4
Admin/staff manually creates engagement letter: open appropriate template in Ignition/GoProposal, manually populate fields from the partner's notes, then route to partner for review and approval.
5
Track the opt-out: add a row to the AI Engagement Letter Tracker spreadsheet with Status: 'Manual — Client Opted Out'. This tracking helps measure the percentage of clients who opt out.

Onboarding Call Notes Template Fields

Note

Note to MSP: If opt-out rate exceeds 20%, investigate root cause: - Is the verbal disclosure script too alarming? - Are specific partners not reading it with the right tone? - Is there a pattern by client type or industry? - Consider revising the disclosure script to emphasize benefits and security.

Note

The firm's service quality should be identical regardless of whether AI was used. The engagement letter should look the same — only the process of creating it differs.

Testing & Validation

  • AUDIO QUALITY TEST: From each speakerphone location, record a 60-second sample conversation using Windows Voice Recorder or macOS QuickTime. Play back and verify: (1) all speakers are clearly audible, (2) no echo or feedback, (3) accounting terms like '1120-S' and 'S-Corp' are distinguishable. Score each location pass/fail.
  • FIREFLIES BOT JOIN TEST: Create a test Zoom/Teams meeting titled 'Onboarding: Test Client ABC'. Verify Fireflies bot auto-joins within 30 seconds of meeting start. Confirm the notification message appears to all participants. If bot does not join, check calendar integration and auto-join settings.
  • TRANSCRIPTION ACCURACY TEST: Conduct a 10-minute scripted mock onboarding call that includes at least 15 accounting-specific terms (entity types, form numbers, dollar amounts). After transcription, compare the AI output against the script. Target: 95%+ accuracy on general speech, 90%+ on accounting terms. If accounting term accuracy is below 90%, add more terms to custom vocabulary.
  • SPEAKER DIARIZATION TEST: Conduct a mock call with 3 participants (partner, client, spouse/business partner). Verify Fireflies correctly identifies and labels each speaker at least 85% of the time. Mislabeled speakers will cause confusion in the transcript and engagement letter.
  • WEBHOOK TRIGGER TEST: After a test transcription completes, verify the Make.com scenario execution log shows a successful trigger within 5 minutes. Check that the webhook payload contains all expected fields (transcript_id, title, participants, duration).
  • PII REDACTION TEST: Include a fake SSN (e.g., '123-45-6789') and fake EIN (e.g., '12-3456789') in a test call transcript. Verify the Make.com text replacement module correctly redacts both before they reach the OpenAI API. Check the OpenAI input in Make.com execution log to confirm redaction.
  • STAGE 1 EXTRACTION TEST: Feed a sample onboarding transcript through the Onboarding Call Transcript Processor prompt. Verify the JSON output: (1) all discussed fields are populated, (2) undiscussed fields are null, (3) client name, entity type, services, and fee amount are 100% accurate, (4) no hallucinated information.
  • STAGE 2 ENGAGEMENT LETTER TEST: Feed the Stage 1 JSON output through the Engagement Letter Draft Generator prompt. Verify: (1) letter follows the correct template structure, (2) all merge fields are populated, (3) [BRACKET] placeholders appear for missing data, (4) tone is professional and appropriate, (5) AI consent clause is included, (6) letter is between 1.5–3 pages.
  • END-TO-END PIPELINE TEST: Conduct a full mock onboarding call covering: new S-Corp tax client, $3,500 annual fee, monthly bookkeeping at $500/month, fiscal year end December 31. Verify the complete pipeline produces an engagement letter draft within 10 minutes of call completion that accurately reflects all discussed terms.
  • NOTIFICATION EMAIL TEST: After an end-to-end test, verify the partner receives the notification email with: (1) correct client name and service type, (2) fee amount and frequency, (3) clickable link to the draft document, (4) list of items requiring attention, (5) clear AI-generated disclaimer.
  • CONSENT WORKFLOW TEST: Have a test participant decline recording consent during the verbal disclosure. Verify: (1) the partner smoothly transitions to manual note-taking, (2) the Fireflies bot is removed or not started, (3) the opt-out is logged in the tracking spreadsheet, (4) an engagement letter is still produced manually within 24 hours.
  • COMPLIANCE DOCUMENTATION TEST: Verify all compliance artifacts are in place: (1) WISP has been updated with AI tool sections, (2) SOC 2 reports have been obtained from Fireflies and OpenAI, (3) engagement letter templates include AI consent and Section 7216 language, (4) verbal disclosure script is printed and available in each office.
  • ERROR RECOVERY TEST: Simulate an OpenAI API failure (temporarily invalidate the API key in Make.com). Verify: (1) Make.com retries twice, (2) after failure, the MSP support email receives an error notification, (3) the transcript is preserved and can be re-processed manually.
  • MULTI-SERVICE TYPE TEST: Conduct a test call where the client needs both tax preparation AND monthly bookkeeping. Verify the system correctly identifies it as a 'Multi-Service' engagement and generates a comprehensive letter covering both service types with separate fee sections.
  • VOLUME TEST: Process 5 test transcripts in rapid succession (simulate a busy day). Verify all 5 complete successfully without timeouts, API rate limiting, or missed webhooks. Check Make.com operation consumption against the plan limit.

Client Handoff

The client handoff session should be a structured 90-minute meeting with the firm's managing partner, all partners/managers who conduct onboarding calls, and the firm's administrative coordinator. Cover the following topics:

1
SYSTEM OVERVIEW (15 min): Walk through the complete workflow from call to engagement letter draft. Show the data flow diagram. Explain what happens at each stage and how long each step takes.
2
LIVE DEMONSTRATION (20 min): Conduct a live mock onboarding call and walk through the entire pipeline in real-time. Show the Fireflies dashboard, Make.com execution, and the resulting engagement letter draft.
3
DAILY WORKFLOW TRAINING (20 min): Hands-on practice for each partner — starting a call, reading the verbal disclosure, verifying Fireflies is recording, reviewing the draft, making edits, and sending for e-signature via Ignition. Cover the opt-out workflow for clients who decline recording.
4
COMPLIANCE REVIEW (15 min): Review the updated WISP sections, engagement letter consent language, Section 7216 consent provisions, and state recording consent requirements. Ensure every partner understands their obligations.
5
TROUBLESHOOTING GUIDE (10 min): Cover the top 5 common issues and resolutions: Fireflies not joining, poor audio quality, inaccurate transcription, draft quality issues, and system errors. Provide the escalation path to MSP support.
6
DOCUMENTATION HANDOFF: Leave behind — (a) Quick Reference Card (laminated, one per office), (b) Standard Operating Procedure document, (c) Verbal Disclosure Script, (d) Troubleshooting FAQ, (e) MSP Support Contact Card with SLA details, (f) Fireflies.ai admin credentials and login instructions, (g) Make.com scenario documentation, (h) Monthly ROI tracking spreadsheet template.
7
SUCCESS CRITERIA REVIEW (10 min): Agree on measurable success criteria — Target: 80% of onboarding calls use the system within 30 days, engagement letter turnaround reduced from 3–5 days to under 4 hours, partner satisfaction score of 4+/5 on draft quality by end of month 2. Schedule 30-day and 90-day review meetings.
8
SIGN-OFF: Both parties sign the project completion acknowledgment documenting what was delivered, agreed-upon support terms, and the maintenance schedule.

Maintenance

ONGOING MAINTENANCE RESPONSIBILITIES: 1. WEEKLY (15 min MSP time): - Check Make.com execution logs for failed scenarios — investigate and resolve any errors - Review OpenAI API usage dashboard — verify spend is within expected range ($5–$15/month) - Scan Fireflies.ai admin dashboard for unusual activity or transcription failures 2. MONTHLY (1–2 hours MSP time): - Review engagement letter quality metrics with the firm (from tracking spreadsheet) - Analyze common edit patterns — if partners cons...

Alternatives

Microsoft Teams Premium with Copilot

Instead of Fireflies.ai + OpenAI, leverage Microsoft Teams Premium ($10/user/month) which includes built-in intelligent meeting recap with AI-generated notes, action items, and task assignments via Microsoft Copilot. Engagement letter generation would still require a separate LLM step but could use Microsoft Copilot Studio or Azure OpenAI Service for a fully Microsoft-native stack. Tradeoffs: PROS: Single vendor ecosystem (Microsoft), no third-party bot joining meetings (better client optic...

Fully Custom Pipeline with Deepgram + AssemblyAI

Replace the SaaS transcription platform entirely with direct API calls to Deepgram (for real-time streaming transcription) or AssemblyAI (for batch transcription with built-in PII redaction). Build a custom web application or use a low-code platform like Retool to create a firm-branded transcription and engagement letter portal.

Engagement Letter Platform Native AI (Ignition AI / GoProposal)

Wait for Ignition and GoProposal to release their own AI-powered engagement letter generation features (both have announced AI roadmap items). Use a simpler transcription-only setup and rely on the engagement letter platform's built-in AI to generate drafts from imported meeting notes rather than building a custom GPT-5.4 pipeline.

Budget Approach: Fathom Free + Manual Letter Creation

Use Fathom's unlimited free transcription tier for all onboarding calls. Partners manually review the AI-generated summary and action items from Fathom, then create engagement letters using existing templates in Word/Google Docs. No automation pipeline, no LLM API costs.

Want early access to the full toolkit?