Muster, by GTM Cloud · Engage · Early access
A Salesforce communication timeline with every channel in one thread
Muster gathers a record’s emails, tasks, events, case comments, files and your own objects into one component. Each kind has its own tab, and an All tab merges them into a single thread, newest first. Add an item or send an email without leaving the record.
You know this one
It’s four in the afternoon and a case lands in your queue, escalated. The customer is already on the phone, and the first thing they say is “I’ve explained this three times.”
You open the case. The emails are in one related list. The comments are in another. The text messages went into a custom object on a tab you haven’t opened since training. There’s a call log, some files, and a task someone closed on Tuesday.
You say “let me read through this”, and the customer hears typing, then silence. Everything you need is in Salesforce. It’s in five places.
One thread for the whole conversation, beside your activity timeline
To muster is to call everyone together in one place. Muster does that for a record’s history: its emails, tasks, events, case comments, files and any custom object that points at it, such as a text-message object.
Each kind of item gets a tab, and the All tab merges them by date, newest first. A rule chooses the tabs for each object, so a Case page and an Account page can show different threads. It sits beside the standard activity timeline and doesn’t replace it.
See it first. Take it back. Keep the receipt.
| Preview | Undo | Prove |
|---|---|---|
| Read the whole history in order before you reply. | Nothing to take back: the thread reads your records and rewrites none of them. | Email sent from the thread is logged on the record. |
What you get
A communication timeline in one chronological thread
The All tab merges every channel by its own date, newest first, with Load More for long histories. Each item is a card with a date, a title link and two summary fields, and expands for more. A tab per channel keeps each kind separate when you want it.
You decide what each page shows
A rule picks the base object, optional conditions and an ordered list of tabs. Starter rule templates get you going.
Act without leaving the record
New creates a task, comment or other item with preset values you define. New Email, Reply, Reply All and Forward work from the record, and the email is logged on it.
Your own objects become tabs
A text-message object, a call log, anything with a lookup to the record. List the lookup once in Settings and use it in a rule.
It runs as the person
People see only the records, tabs and fields they can already read. A Read Only user sees the thread without a New button.
How it works
- Assign access. Give admins Muster Admin and everyone else one of the other sets.
- Check Settings. Review the enabled objects and relationship mappings.
- Start from a template. Pick the template for your object, such as Case, and save it.
- Place it. Drag the component onto the record page, leave Rule on Automatic, then save and activate.
Two readers, two reasons
If you’re the admin
A rule picks the base object, optional conditions and an ordered list of tabs. Add your own objects by listing their lookup once in Settings. Rules, not code.
If you’re the one signing off
Customers notice when the person replying hasn’t read the history. Muster puts the whole conversation in front of whoever picks up the record, so nobody asks the customer to repeat themselves.
Today, and with Muster
| Today | With Muster |
|---|---|
| History spread over several related lists | One thread with a tab per kind of item |
| No single time-ordered view of a customer | A newest-first thread on the All tab |
| New items created on different screens, with no preset values | New and email actions with preset values |
| Custom objects that nobody remembers to check | Your own objects as tabs |
Where it’s strong, and what to know first
We’d rather you find the limits here than after you install.
Where Muster is strong
- One chronological thread instead of five related lists
- A tab for each kind of item when you want to see them separately
- Create a task, a comment or another item from the thread, with preset values
- New Email, Reply, Reply All and Forward from the record
- Your own objects, such as a text-message object or a call log, become tabs
Good to know before you install
- Muster shows what’s already in Salesforce. It doesn’t connect to a mailbox or capture email by itself.
- The email-sending screens are in English for now. The rest of the app is in five languages.
- A custom object needs a lookup to the record before it can become a tab.
Questions people ask
How do I see every email, task and comment on a Salesforce case in one place?
With Muster, you add one component to the Case page. Its All tab merges emails, tasks, events, case comments and files into a single thread, newest first, and each kind also has its own tab. A rule chooses which tabs a Case page shows.
Will people see things they shouldn’t?
No. Muster runs as the person, so nobody sees a record, a tab or a field they couldn’t already read. A Read Only user sees the thread without a New button, so they can follow a case without being able to add to it.
Can we include our text messages or call logs?
Yes, if they’re records with a lookup to the base record. List the lookup once in Settings and use it in a rule, and the object becomes a tab beside emails and tasks. Without that lookup, an object can’t become a tab.
Does it replace the Activity timeline?
It sits beside it. Use Muster where a team needs every channel in one time-ordered view, and keep the standard components where they already work. Muster is a component you place, so you decide which record pages carry it and which keep the standard view.
Does it connect to our mailbox?
No. Muster shows what’s already in Salesforce and doesn’t capture email by itself. It does let you send email from the record: New Email, Reply, Reply All and Forward are all there, and what you send is logged on the record.
Where can it be placed?
On record pages and in the Utility Bar. It follows the standard refresh on record pages and has its own Refresh button. A rule picks the tabs for each base object, so a Case page and an Account page can each show a different thread.
Works well with
- Rigging: the thread shows what was said. Rigging shows who reports to whom on the same account.
- Pennant: put the warning in a banner on the record, with the thread beneath it.
- Sluice: find and merge duplicates, with an undo, so there’s one record to open.
Muster is part of the Engage stage of the lead-to-renewal map. Not sure where to start? Book a Data Health Check. Every app installs by itself. None needs another.
Built on the platform
- Native to Salesforce. Rules live in your org as Custom Metadata, and email is sent through the platform and logged on the record.
- Runs as the person, so nobody sees what they couldn’t already read.
- Three permission sets, with Create and Send Email custom permissions for finer control.
- Interface and in-app guides in English, German, Spanish, French (Canada) and Portuguese (Brazil). The new email-sending screens are English for now.
Open your busiest case and count the clicks
Ask for early access and a walk-through on your own Case or Account page. See every channel in one thread, then reply from it.