How to Send Handwritten Notes Automatically from Wealthbox CRM

An advisor marks an opportunity Won in Wealthbox on a Thursday afternoon. The new client has just moved a retirement account over after six weeks of deliberating, two meetings, and one long phone call about a prior advisor who never returned messages. The workflow fires: a welcome email, a DocuSign packet, a task for the associate to schedule the onboarding call. All of it necessary. None of it the kind of thing anyone keeps.

The detail that would have made the first week memorable — that they chose you specifically because the last firm went quiet — is sitting in the note the advisor typed after the second meeting. Nothing in the workflow uses it. A handwritten card that does, mailed the day the account funds, is the one piece of onboarding the client will mention to a friend. Wealthbox already holds every signal needed to send it. The gap is that those signals currently produce tasks and emails, and the fix is a thirty-minute Zap.

The Wealthbox moments worth a stamp

Wealthbox is built around contacts, opportunities, workflows, and tags, and nearly everything an advisory firm does leaves a mark on one of them. That makes it tempting to fire a card off every event. Resist it. A card after every task completion stops being a gesture and becomes a mailer, and a firm's clients are precisely the people who recognize a mailer. Four triggers account for almost all of the return.

An opportunity closes Won

The strongest single moment. A new client has just made a decision they spent weeks on and is still deciding whether it was the right one — the window a card lands in hardest. Pull from the opportunity: the stage history, the amount, the source, and the notes the advisor left along the way. The broader argument for which advisory moments deserve a note is in handwritten notes for financial advisors.

A workflow step completes

Most firms run onboarding, annual review, and account-transfer processes as Wealthbox workflows, and a completed step is a cleaner trigger than a status field because it marks something that actually happened. The step after an account funds, the step that closes out an annual review, the final step of an estate or beneficiary update — each is a moment the client felt, and each already fires a Zapier trigger without any new field being built.

An important date comes around

Wealthbox keeps birthdays, anniversaries, and client-since dates as important dates on the contact, which is exactly the kind of data that makes an anniversary card possible without anyone remembering to send one. A five-year client-since note, written from what the relationship has actually covered, outperforms every birthday card in the stack. Automated birthday cards for customers covers how to keep these from reading as a calendar reminder.

A tag gets applied

Tags are how Wealthbox users mark the things that don't fit a workflow — referred a friend, lost a spouse, retired this year, moved. A tag for a referral is the best low-volume trigger in the system, because the person being thanked is already warm and the card is the only acknowledgement that doesn't feel transactional. A tag for a loss should route to a card as well, but one that is read by a human before it mails; sympathy card messages for clients covers why that one never runs automatically.

Setting it up

Wealthbox does not expose native outbound webhooks, so the path is Zapier, which Wealthbox supports directly with triggers for new contacts, notes, tasks, events, opportunities, workflows, and completed workflow steps. That is enough to reach every trigger above. A Zap watches the Wealthbox event, filters it to the condition you care about, and hands the contact to Scribble; the whole thing takes less time than the first onboarding call.

• ✓Connect Wealthbox to Zapier with an API access token from the Wealthbox settings page, then connect Scribble on the action side.
• ✓Pick the trigger. Workflow Step Completed is the most precise; New Opportunity with a filter on stage equals Won is the most common starting point; New Note with a filter on a tag works for referrals and life events.
• ✓Set tone or a template per trigger so a welcome card doesn't read like an anniversary card, and so the referral thank-you doesn't sound like onboarding.
• ✓Map the mailing address deliberately. Wealthbox contacts often carry a home address, a mailing address, and a household address that differs from the individual's, and nearly every misdelivered card traces back to picking the wrong one. Households matter here: a card to a couple should go once, to the household, not twice.
• ✓Choose a control mode: fully automatic, notify-only, a review window that auto-approves after a set number of hours, or approve-each. Advisory firms with a compliance review step usually start on approve-each and move to a review window once the drafts stop needing edits.
• ✓Send a test card to your own address and read it out loud before turning the Zap on for live clients.

Turning Wealthbox fields into copy that doesn't sound like a merge

This is where most automated client mail gives itself away. A merge template produces 'Welcome to the firm, {{first_name}}' at scale, and a client who has just handed over their retirement savings notices the seam in the first line. For a channel whose entire value is that it doesn't read as automated, that is a strange way to fail.

The fix is letting the record write the sentences. Scribble drafts each card from what the Wealthbox contact actually holds — the opportunity source, the note from the second meeting, the workflow that just finished, the client-since year — so two clients onboarded the same week get genuinely different cards. The advisor's own notes are the richest source, which is a good reason to keep writing them: a sentence typed after a meeting becomes the sentence on the card.

The point of connecting Wealthbox is not to send more cards. It is to send cards that could only have been written to that one client.

Compliance deserves a word. Nothing in a thank-you or anniversary card should reference performance, returns, or a recommendation, and a template per trigger is the simplest way to guarantee it. Firms that archive client correspondence can log each card's text back to the contact so it sits with the rest of the record — see the next section — which usually satisfies the books-and-records question before it is asked.

Writing results back to Wealthbox

An integration that only sends is half an integration. Use a second Zap, or the same one, to create a note on the Wealthbox contact when the card mails — the text, the trigger, the date — so the next associate who opens the record knows a card already went out and does not send a second. Route response signals back in the same way: a QR code on the card can apply a tag, create a task for the advisor, or log an activity on scan, which turns a physical card into something Wealthbox can actually see.

That write-back is also what answers the question when a partner asks what the handwritten mail line is doing. The answer becomes tagged referrals and logged activity inside Wealthbox, next to the opportunities they produced, rather than a shipment count sitting in a separate tool.

A sensible rollout

Start with one Zap, not five. Opportunity Won, or the onboarding workflow's funding step if that is how your firm marks a new relationship, is almost always the right first trigger. Run it in review-window mode for a few weeks so every card gets a look before it mails but nothing stalls during a busy stretch. Once the drafts stop needing edits, move it to fully automatic and add the second trigger — the client-since anniversary is usually the best follow-up, because the volume is steady and every recipient is already a client. If the trigger you want lives partly in another system, such as a custodian feed or a planning tool, the Zapier route combines them the same way. Firms on Salesforce Financial Services Cloud have a direct path instead.