AssociatesCRM Platform
Drag to reorder · toggle active to show/hide in the quote tool
Each band multiplies the base price of band-scaled services. Band 0 (Nil) must have multiplier 1. Changes apply immediately when saved.
| # | Label | Multiplier |
|---|
When a client has more than one company / business with MSF, a banded discount comes off all fees. It is applied first, before any manual discount. Set the number of companies on each proposal (Companies with MSF). Internal only — never shown to clients. Each row: from this many companies, apply this % off. The highest band the count reaches wins.
| From (companies) | Discount % |
|---|
x-xama-secret. Webhook URL to enter in Xama: https://dokodopvdhvzrqbthejk.supabase.co/functions/v1/xama-webhookFirm-wide constants merged into every Letter of Engagement and the Terms & Conditions — supervisory body, complaints body, insurer details and default notice period.
One letter template per entity type, merged with deal-specific details (primary officer, manager, start date, fees) when a Letter of Engagement is generated. Every letter automatically bundles the Schedule of Services for each enabled service and the Terms & Conditions below.
Write the responsibilities text for each service. These are bundled after the Engagement Letter for every enabled service on the deal.
This text is shown on the client's proposal page when T&C is enabled on a share link. HTML supported.
Shown on the client's proposal, before the approval step: the onboarding roadmap ("what happens after you approve") and your "our promises to you" block. Edits apply to new proposals; already-sent ones keep what they were sent with. Leave a section empty to hide it.
Sent automatically to the client the moment they sign a proposal (or Letter of Engagement) — their signed Proposal PDF, and the LoE PDF if one was bundled, are attached automatically. We're BCC'd at hello@msfassociates.co.uk. HTML supported.
Tokens: [FirmName] [ClientName] [PrimaryContact] [PrimaryContactFirstName] [CurrentDate]
Used by the "Draft email" button on deals. Drafts are created in Missive for review — nothing sends automatically. Placeholders: {{first_name}}, {{last_name}}, {{company}}, {{my_name}}.
Named bundles of tasks — e.g. New Client Onboarding, Adding Payroll, Annual Accounts only. When a deal is marked won you pick which one applies, and any deal's checklist can have one added at any time, so an existing client taking on one more service does not get the whole onboarding.
Changes save instantly. Checklists already on a deal are not affected.
Connect your Brevo account to manage email lists and trigger automation workflows directly from contact pages.
Find your key: Brevo → Settings → API Keys → v3 API key.
Your Brevo lists — available in contact page dropdowns for list management and automation triggers.
Used for BCC email capture — any email BCC'd to your inbound address is automatically logged on the contact page.
yanuuheloo.resend.app
BCC any outbound email to bcc+{token}@yanuuheloo.resend.app to auto-log it on the deal or contact page.
Connect your GHL (LeadConnector) location. GHL is treated as the master for contacts and pipeline — this app pushes proposal data and status into GHL, and syncs contacts & opportunities. Uses a Private Integration token (Settings → Private Integrations in GHL), scoped to one location.
In GHL: Settings → Private Integrations → create a token with Contacts and Opportunities scopes (read & write).
Your GHL sub-account (location) ID — Settings → Business Info, or the ID in your GHL URL.
When a deal is pushed to GHL it becomes an Opportunity in the pipeline below, at the stage mapped from your CRM stage. Load your GHL pipelines, pick one, map each stage, and save.
Each adviser connects their own Microsoft 365 account. Calendar sync (activities, bookings) comes with the basic connection. Email auto-logging — emails you send to or receive from a deal's contact appearing on the deal card automatically, no BCC needed — is a one-time extra permission per person.
Microsoft will ask you to approve "Read your mail". We only read messages exchanged with a deal's contact, and only when that deal is open — nothing is stored beyond the subject, preview and a link back to Outlook.
Meetings are now booked through MSF Bookings — our own scheduling pages, built into the hub. Set your booking pages, weekly hours and link handle in the Bookings app; the "📅 Book" button on a deal opens your page prefilled and the meeting lands on the timeline automatically.
The "📅 Book meeting" button on a deal opens this link prefilled with the contact's name and email. Each adviser sets their own.
Create one at Calendly → Integrations → API & Webhooks → Personal access tokens. Stored once for the whole firm.
Brings Fathom and Fireflies calls onto the client profiles. A call is matched on the attendee who is not one of us, and never linked outright — it appears as a suggestion on that client's Connections tab for someone to confirm. Until then the call is kept but shown against nobody.
Each person adds their own key below — one key for the whole practice would only ever see one person's recordings. A sync then pulls from every connected account at once. Your key is yours: nobody else can read it, not even an admin, and a call two of you were both on is still stored once.
MSF_OUR_DOMAINS still belongs in Supabase under Edge Functions → Secrets — it says which email domains are ours, so a call is matched on the client rather than on us.
Better than syncing: Fathom pushes each call here the moment it is ready, so it reaches the client profile within a minute of the call ending, with no key and no polling. Paste this URL into Fathom's webhook settings, then put the secret Fathom gives you into FATHOM_WEBHOOK_SECRET in Supabase under Edge Functions → Secrets. Until that secret is set the endpoint refuses everything, because anyone can find the URL.
Where your deals & contacts come from. These appear in the source dropdowns on deals and contacts, colour the pills on the board, and drive the Revenue by Source report. Rename or recolour freely — existing deals keep their stored source text, so keep the name if you just want a new colour.
Your sales stages — the columns on the deals board before a deal is won. Add, rename, recolour and reorder them here. Onboarding, Won, Lost and Nurture are fixed system stages (they carry onboarding, AML and win-rate logic) and aren't editable. If you remove a stage that still has deals in it, those deals stay safe and appear in an “Unsorted” column on the board until you drag them elsewhere.
Every lead captured on the event form records who took it. Match each capturer to a team member below and assign in one go. By default only unassigned leads are touched, so this won’t overwrite anything you’ve already set.