When Nothing Arrives After a Meeting
Separating a missing recording from a missing setting.
There are two quite different problems here and they look identical from your inbox.
Nothing was recorded, so there was no transcript, so none of the four post-meeting actions had anything to act on. This is the common case by a wide margin.
Something was recorded and processed, but an action did not run or did not reach anybody. This is a setting or a dependency.
The first question separates them, so start there rather than with the setting you were expecting to blame.
Troubleshooting Guide
Does the meeting have a transcript on its screen?
Does the meeting show a summary and highlights as well as a transcript?
Is the specific action switched on at Settings → Sales Settings → Meeting Settings?
Did your debrief arrive while the attendees heard nothing?
Did the contact record not update?
Was the meeting processed before you changed the setting?
Known Issues
No debrief arrived at all
Most often the meeting was never recorded.
Open the meeting. If there is no transcript, nothing was recorded and the debrief had nothing to report — look at the Observer rather than the debrief setting.
If there is a transcript and a summary, check that Email me a meeting debrief is on. It is on by default, so somebody has turned it off.
A third and rarer cause: Zyntro could not work out which member organised the meeting, so there was nobody to address it to. The meeting's attendee list will show no host in that case.
My debrief arrives but the attendees never hear anything
No verified sending domain, or the summary setting is off.
This exact pattern has one usual cause. The debrief goes out through Zyntro's own email sending and needs nothing configured. The attendee summary goes from your own domain, so without a verified sending domain Zyntro skips it rather than sending a message that appears to be from you.
Check Send the attendees a summary is on, then check your organisation's sending domain. Then test with a real meeting and an outside email address.
One attendee got the summary and another did not
The one who did not is opted out, or has no valid address.
Anyone whose contact record is marked as opted out of email, or as do-not-contact, is skipped — a meeting summary is still an email they did not ask for. An invalid or missing address is skipped too.
The host is always excluded by design; the organiser gets the debrief instead.
The contact record did not change
The setting is off, or there is no contact on the meeting.
Update the contact record from what was said is off by default — check that first.
If it is on, check the meeting's attendee list. A typed-in name is not a contact record, so there is nothing to write to. Only attendees with a View Contact link count.
If both are fine, remember that inferred details are applied only where Zyntro was confident. Something mentioned ambiguously is deliberately left alone, and you would find it in the transcript rather than on the record.
No follow-up reminder appeared
The setting is off, or no follow-up was recommended.
Work out the follow-up is off by default.
With it on, check the meeting's Follow-up Recommended section. If there is nothing there, none was recommended — a meeting that concluded cleanly often needs no follow-up, and the reasoning says so.
If the recommendation is there and no reminder appeared, note that re-processing a meeting does not create a second reminder. One already existing is the usual explanation.
A summary went to clients about meetings from weeks ago
A batch of old meetings was processed without suppressing notifications.
The recovery panel on an existing meeting has Suppress attendee notifications on by default for this reason, but the Retrospective screen has it off.
When catching up on old meetings, check that toggle before each submission. If it has already happened, the practical response is a short note to anyone affected — the messages were sent as you, so they read as yours.
I changed the settings and the last meeting still behaved the old way
Settings apply going forward.
A meeting that has already been processed is not re-run when you change a setting. Process the recording again to apply the new settings to that meeting.
Re-processing is charged at the same rate as the original, so it is worth getting the settings right before a run of important meetings rather than afterwards.
Nothing has worked since a particular date
A Google Meet connection lapsed.
If several meetings in a row produced nothing, the cause is upstream of all four actions.
Look at the connection roster on Meeting Settings, which lists every Google Meet connection in the organisation and flags the ones needing renewal. Meetings booked during a lapse were created without a Google Meet link and cannot be recorded even after reconnecting.
Frequently Asked Questions
Only the debrief to you. The attendee summary, the contact update and the follow-up are all off. A workspace that has never opened Meeting Settings is producing full intelligence and emailing you about it while writing nothing to the CRM and sending nothing to anyone else.
No — processing is a single pass. Change the setting and process the recording again, which re-runs everything that is switched on.
No. Settings apply to meetings processed after you save them. Already-processed meetings are untouched unless you process them again.
It goes out through Zyntro's own email sending, which needs no setup. Everything addressed to people outside your business goes from your own domain and needs that domain verified. That one difference explains most of the asymmetry people notice.
Only through the attendee summary, and only if you switch it on. The follow-up is a reminder addressed to you — it never messages the contact.
No. Skipped means there was nothing to do: everyone had opted out, there was no contact to write to, or no follow-up was warranted. Each skip records its reason, which is different from something failing.
Tip: One check answers most of these: does the meeting have a transcript? If it does not, nothing downstream could have happened and the settings are irrelevant. If it does, the problem is one setting or one dependency, and the sections above name which.
