What lands in Redtail after a client meeting
One note for the meeting, and the tasks you pick. The exact text Redtail receives, and what Mesh leaves alone.
The note: One plain-text record of the meeting
When you push a meeting from Mesh to Redtail, one note carries the record of that meeting. Someone may print it, export it, or read it years later without the fields around it. So Mesh writes the note to stand on its own.
The note is plain text. Redtail shows a note body as it is, so formatting marks would arrive as stray asterisks and pound signs. Mesh removes them before the note leaves. Each section has a label in capital letters on its own line, and each list item starts with a hyphen.
MEETING NOTE Meeting: Annual Review: Robert & Susan Caldwell Date: Thu, Oct 1, 2026, 58 minutes Method: Meeting Assistant joined the call Attendees: Robert Caldwell (participant); Susan Caldwell (participant) SUMMARY Dana Whitaker met with Robert and Susan Caldwell for their annual review. They confirmed Susan's retirement at 62 and Robert's at 64. Dana Whitaker recommended a Roth conversion for 2026 that keeps them in their current tax bracket, and the Caldwells agreed. Dana Whitaker will correct the IRA beneficiary designation, and Susan Caldwell will send the 529 statement this week. ACTION ITEMS Advisor - Submit the beneficiary-change form to the custodian (due Fri, Oct 30, 2026) - Book the 2026 Roth conversion (due Fri, Nov 13, 2026) Client - Susan Caldwell: Send the 529 statement for tuition planning (timing: this week) Prepared by Mesh from a meeting transcript. Reviewed by Dana Whitaker.
Read it from the top. The header names the meeting, the date and the length, how the meeting was recorded, and who attended, with a role for each person. Dates use a short month name, so no reader has to guess the order of day and month. The meeting date is in your workspace time zone.
SUMMARY holds the brief summary of the meeting, with its formatting removed. ACTION ITEMS lists each open item under the person who owns it: Advisor first, then Client, with the client’s name in front of their step. Items you already marked complete are left out. An empty section says “None recorded”, so a reader can tell that nothing came up.
A due date appears only when someone named one. If your client said “this week”, the note keeps those words as the timing. If nobody gave a time, the line says “no date set”. Mesh does not guess a date for you.
The last line says that Mesh prepared the note from a meeting transcript, and names you as the reviewer.
The push: You see the exact note first
The push is the fourth step of the review on the meeting page. The step shows the client that the note files under, and one button: Push to Redtail.
Push to Redtail
Review the exact note and tasks, then push. Nothing writes back without you.
The approved summary posts as a meeting note, and you pick which of the 3 action items push as Redtail tasks.
The button does not write anything yet. It opens the push window. The note is at the top, in a text box you can edit. On the first push, what you leave in that box is what Redtail receives, so fix a name or cut a sentence there.
Under the note is the list of the meeting’s action items, each with a checkbox. Every item that is not in Redtail yet starts checked. Clear the ones you want to keep out of your CRM, then push.
Nothing writes back without you. The push happens when you press the button, or when a workflow that you set up runs, for example one that pushes action items after each meeting. A workflow like that pushes each action item as its own task, with no note and no push window.
What pushes: A note, your tasks, and nothing else
A push from the push window files activities in Redtail. It does not change anything else there. Here is the full list.
| Item | Pushes | In Redtail |
|---|---|---|
| The meeting note | Yes | One activity, dated on the meeting day, with the note as its text |
| Action items you check | Yes | One task each, dated on its due date when it has one |
| Action items you clear | No | They stay in Mesh |
| Compliance flags | No | They stay in Mesh, for your review |
| Your client’s contact record | No | The push does not edit it |
| Contacts | No | They sync the other way, from Redtail into Mesh |
Each task keeps the title and the priority of its action item. A step that your client owns starts with the person you are waiting on, for example Waiting on Susan Caldwell: Send the 529 statement for tuition planning.
Redtail assigns a task to a user, not to a name. So Mesh puts the owner where you will see it: in the subject of a client’s step, and on an Owner line at the top of the task description.
A task with a due date is dated on that day. A task with no due date still gets a date in Redtail, because Redtail requires one. Check those items before you push.
Mesh does not put compliance flags in the note. They are part of your review in Mesh, not part of your client’s CRM record. How compliance flags work.
After the push: One copy, filed under your client
When the meeting’s client is a contact that Mesh synced from Redtail, the note and the tasks link to that contact. They show on that client’s record in Redtail, not as loose activities.
Mesh keeps a log of every push and its result. That log is why a second push does not file a second note. If Mesh already filed the note for that client, a second push does not send the note again. Mesh returns the note it filed, and edits in the text box do not reach Redtail. To change a filed note, edit it in Redtail. Checked tasks that Mesh has not pushed yet still push. In the push window, an item that already pushed shows “Already pushed”, and you cannot select it again.
In the push window, the note goes first. If Redtail does not accept it, Mesh does not push the tasks, so a failed push does not leave tasks without their note. When the push works, each row in the window shows a check mark and a link to the new activity in Redtail.
Before you push, read the note once as a stranger would. It is the version of the meeting that your firm keeps. This post covers Redtail. Wealthbox is coming soon.
Next: Your next meeting, written up
Request early access to try Mesh on your own client meetings. Nothing goes to a client until you approve it. Notes and tasks go to Redtail when you push them, or when a workflow you set up runs.