Review and sync meeting results

​

Post-Meeting: Summaries & ATS Sync

​

Summary Generation (Interview)

Once the meeting bot or a live recording session finishes recording an interview (either when the meeting ends, the bot is manually removed, or recording is stopped), a summary is automatically generated. The summary:

• Is formatted in markdown.
• Incorporates the template’s summary format configuration (note sections + custom sections).
• Appears in the Summary tab of the note view.
• Can be copied to clipboard using the copy button.

​

Job Description Generation (Intake)

For intake meetings, Tenzo generates job descriptions after the bot or live recording session finishes:

1. Each job description template on the preset is rendered with details extracted from the conversation (title, requirements, responsibilities, etc.). When your ATS exposes multiple description fields, every field’s template is rendered into its own job description; otherwise the single generic template produces one job description.
2. Tenzo extracts job-field values from the transcript. With an ATS, that uses the fields selected in the template’s ATS Job Sync list (e.g. salary, start date, employment type, location). Without an ATS, Tenzo extracts against its built-in Job Sync fields (title, description, location, and related job details).
3. The generated job descriptions appear in the Job Description tab of the note view. The tab shows every generated description — one per ATS description field, each labeled by its field name (or a single description when there are no ATS fields). Each one can be regenerated individually, so you can re-run just the internal or just the public version without touching the others, and copied to clipboard with its copy button — the copy keeps the description’s formatting, so pasting into a rich-text editor (or your ATS) preserves it.

​

Summary / JD Email

After generation, an email is sent to the configured recipient (or meeting organizer) containing the output.

• Interview notes receive the HTML meeting summary plus a link back to the full note in Tenzo.
• Intake notes receive the rendered HTML job description plus a field-by-field preview of the ATS writes that will (or did) happen — each row shows the field name, the current ATS value, and the newly extracted value, so you can eyeball the diff before the write lands.

When your organization has an ATS integration, the intake email deep-links to the note’s ATS Sync tab (and includes a short footer pointing there) so you can finish creating the job or push fields. If the note isn’t linked to a job, the email also includes short instructions for how to link one so the JD can sync to the ATS. When your organization has no ATS integration, the intake email deep-links to the note’s Job Sync tab instead. Use that tab to review extracted fields, fill any create-required gaps (job title and job description), and create the Tenzo Job — which also starts AI interview script generation. Tenzo only creates the Job automatically after the meeting when the note’s sync toggle is on and every create-required field was already filled by extraction; otherwise no Job is created and you finish it from Job Sync. You can always open Job Sync afterward to update fields (updates regenerate the interview script). If the ATS job couldn’t be created or updated, the intake email opens with a prominent Action Required banner explaining the failure and linking to the ATS Sync tab so you can finish the create or push the fields manually.

​

Intake Context for AI Interview Scripts

When Tenzo generates or regenerates an AI interview script for a Job, it looks up Meeting Copilot or Autopilot intake notes linked to that Job — either by the Tenzo Job itself or by the linked ATS job id — and uses the AI Interview Script Context from those notes, or their meeting summary when that context is unavailable, alongside the job description. That lets screening questions, intros, and outreach copy reflect what was discussed in the Meeting Copilot / Autopilot intake (must-haves, compensation, nuances) instead of relying on the JD alone. If no linked intake note exists, generation falls back to the job description.

​

ATS Sync / Job Sync

Interview notes — If configured in the template’s summary format, the summary is automatically posted to your ATS:

• Candidate record — The summary appears as a note on the candidate’s profile.
• Application record — The summary appears as a note on the specific application.
• Both — Posted to both locations.

Intake notes with an ATS — If any fields are selected in the template’s ATS Job Sync list (and the note is linked to a job), Tenzo writes each selected field directly onto the ATS job record:

• Description fields are populated with their rendered HTML job description — each description field gets the body generated from its own template.
• Non-description fields are populated with the values extracted from the transcript.
• Per-note overrides on the Config tab narrow what’s written for that specific note.

This sync happens automatically in the background after generation. Automatic intake job sync is currently supported for Bullhorn and JobDiva — for other ATS providers no fields are written automatically, though you can still push fields manually from the note’s ATS Sync tab. The note’s ATS Sync tab appears when the account has an ATS integration that supports job creation and sync. If the panel is reached without a supported ATS write path, it explains why instead of showing the field table. After creating or syncing a job, the displayed job values refresh while your field selections and edited values stay in place. If several refreshes overlap, the latest refresh supplies the displayed values. Intake notes without an ATS (Job Sync) — The same Sync tab is labeled Job Sync and uses Tenzo’s built-in job fields:

1. After the meeting, Tenzo extracts job title, description, and related fields from the transcript (plus the generated job description).
2. Create is available once create-required fields are filled — currently Job Title and Job Description. You can finish any gaps in the Job Sync table, then click create. If Create Tenzo screen is on and extraction already filled those fields, Tenzo creates the Job automatically after the meeting. With the setting off, or with either field still missing, you finish the create manually from Job Sync. The Job remains paused for review.
3. Creating the Job also starts AI interview script generation and links the note to the Job, so the Sourcing tab appears (see Source Candidates).
4. Later updates from Job Sync write into the Tenzo Job and re-run script generation so the interview script stays aligned with the latest job details. The panel explains this before you sync.
5. If you unlink the Job in Config, Job Sync returns to creation mode.

​

Note action by meeting type

When a summary is posted as a note, the note’s action reflects the meeting type, so each meeting type is easy to distinguish (and filter) in your ATS. For Bullhorn, the default action labels are: These defaults can be customized per organization. Reach out to Tenzo if you’d like different note-action labels for your Bullhorn instance. Bullhorn instances that validate Note.action values must have all five labels above configured as valid actions before summaries will post under the intended categories.

​

Creating a company or contact from the picker

When you create a new job from a note, the ATS Sync tab (reading Creating a new ATS job) asks you to pick the client company and hiring contact from your ATS. Tenzo searches your ATS by name as you type. If the record doesn’t exist yet — for example a brand-new client discussed in the intake — the picker offers a Create new company / Create new contact option for the name currently in the search box after its search finishes with no matches.

• Selecting it shows a short confirmation (the entity type, the name, and — for a contact — the parent company) before anything is written.
• On confirmation, Tenzo creates the record directly in your ATS and selects it, so you can finish creating the job without leaving Tenzo.
• A contact is always created under the company you’ve already picked, so choose the company first. Tenzo splits the typed name into a first and last name on the final space.

This is available for Bullhorn only. For other ATS providers the picker is search-only — create the record in your ATS first, then search for it here.

​

Job Owner

The ATS Sync panel includes an optional Job Owner picker alongside the company and contact fields. Search your ATS users by name and select who should own the job. Unlike company and contact, leaving it blank never blocks the create — Tenzo falls back automatically. When the job is created, the owner is resolved in this order, stopping at the first that applies:

1. The owner you picked in the ATS Sync panel for this note.
2. The note creator, matched to an ATS user by email.
3. The template’s default owner (set in the preset’s ATS Job Sync sub-section), used when the creator can’t be matched.
4. Your ATS’s own default owner logic, when none of the above resolve.

This is available for Bullhorn only.

​

Viewing Notes After a Meeting

There are several ways to access completed meeting notes:

​

Meeting Copilot Dashboard

Navigate to Meeting Copilot in the sidebar and open the Notes tab to see all notes. Click any note to view the full details, including the transcript, notes, summary, and chat history.

​

Candidate Interview Tab

For notes linked to a specific candidate, the meeting summary and notes will also appear on the candidate’s Interview tab within their profile. This provides interviewers and hiring managers quick access to meeting outcomes directly from the candidate view.

​

ATS

If ATS sync is enabled, summaries are available directly in your ATS on the candidate or application record (depending on configuration).