How to Track Commitments Made on Sales Calls: Types, Owners, a Register Template and a Weekly Review

Last updated November 2026.

To track commitments made on sales calls, write each promise in the customer's words within a day of the call, classify it by type, give it a named delivery owner and a customer-facing due date, keep it in one commitment register with a status, review open items by account every week, and hand each one to delivery with the quote and recording link attached. A spreadsheet is enough to start. BuildBetter can automate capture and follow-up once volume outgrows manual logging. This guide covers the method, a copyable register template and a hypothetical worked example.

What counts as a commitment on a sales call

A commitment is anything your company tells a named customer it will do, where someone other than the speaker has to deliver it. Examples include “SSO ships next quarter,” “We can lift the retention cap for you,” and “You'll be live in under a week.”

It is not a note, an action item or a next step, because those belong to the person who wrote them. A commitment belongs to a team that was not in the room, usually product, engineering, security or customer success. It is usually made by a rep trying to close a deal.

Exclude two things explicitly, or the register will fill with noise:

• Requests you did not agree to. “Do you support SCIM?” followed by “not today” is a feature request. Track it, but in a separate place.
• The rep's own follow-ups. “I'll send the deck” is a task for the rep. It goes in the CRM task list, not the register.

Conditional promises do count. “If that's a blocker, we can look at it for Q3” sounds hedged to the rep, but the buyer hears a yes. Log it, and mark its strength as conditional so the owner knows exactly what was said.

Commitment types and who owns each

Most sales-call commitments fall into six types, and each one has a natural owner outside sales. For the wider view across the whole deal cycle, see how to track promises sales makes to customers.

Two ownership rules make this work. First, the delivery owner is a person, not a department, because “Product” does not read the register. Second, the account owner owns the register as a whole. That is usually the AE before signature and the CSM after. The account owner keeps the register complete, runs the weekly review and tells the customer the outcome.

Where commitments get made

Commitments get made in five recurring moments, and most teams only watch the first one.

The last two moments carry the most risk. Senior people make those promises under pressure to keep an account, and they are the least likely to be written down. Apply the same register to them, not only to new-business calls.

Why commitments get lost

Commitments get lost at handoffs, not on the call. The failure usually follows four steps:

1. The promise is verbal, made near the end of a call, often as a conditional.
2. The CRM note is clean but incomplete. The CRM has fields for stage, amount and close date, but none for “things we said we would do.”
3. A ticket strips the customer. “Improve bulk actions” no longer says who asked or by when.
4. The work ships, or does not, and nobody can answer “who was waiting for this?”

Here is the tell that this is happening to you. A customer raises something in a QBR, and your team debates whether it was ever promised. If that debate is possible, you are not tracking commitments.

The commitment register: fields, due dates and status

A commitment register is one table with one row per commitment. The account owner owns it, and everyone who delivers can read it. These are the fields:

• ID, so tickets and emails can reference the row.
• Account and deal, matching your CRM names exactly.
• Said by / said to, meaning your speaker, plus the customer's name and title.
• Date made and source link, meaning the recording link with a timestamp.
• Exact quote, in the words actually spoken, not a summary.
• Type and strength, where strength is firm, conditional or exploratory.
• Delivery owner, which must be a named person.
• Customer-facing due date and internal target date.
• Status and at-risk flag.
• Delivery link, meaning the Jira or Linear ticket or the onboarding plan.
• Customer notified on, plus decision notes.

Due dates

Every row should carry two dates. The customer-facing date is the latest date the customer would still consider on time. If they heard “Q3,” use the last day of Q3. The internal target date is the owner's plan. Flag any row where the internal date falls after the customer date.

If no date was said, write “none stated” and ask in the recap email. A blank date field is the most common way commitments drift.

Status values

Use six statuses. Captured means logged but not yet accepted. Accepted means the owner agreed and a date is set. In progress and Delivered follow. Closed means the customer has been told. Declined means you decided not to do it.

Two rules apply. Only the delivery owner moves a row to Accepted. Only the account owner moves a row to Closed or tells the customer about a Declined row. Declined matters as much as Delivered, because a quietly abandoned promise surfaces at renewal.

Copyable register template

Paste this into a spreadsheet and split it on commas. The second row is a hypothetical example.

id,account,deal,said_by,said_to,date_made,source_link,exact_quote,type,strength,delivery_owner,customer_due_date,internal_target_date,status,at_risk,delivery_link,customer_notified_on,decision_notes
C-001,Example Co,Example Co new business,AE name,Buyer name and title,2026-11-03,recording link at 41:10,We can have SSO live before your security review,Security,Firm,PM name,2026-12-31,2026-12-15,Accepted,No,ticket link,,

How to catch commitments in call transcripts

Catch commitments by reading the last ten minutes of each transcript within 24 hours and searching it for promise language. Commitments cluster near the end of a call, when the buyer asks about blockers and the rep tries to remove them. Search for phrases like these:

• “We can…”, “We'll…”, “We will…”
• “By [month or quarter]” or “before your [renewal, launch, review]”
• “That's on the roadmap” or “that's coming”
• “Let me get that turned on for you”
• “I'll check with engineering and come back to you.” This commits you to an answer, owned by whoever has to give it.
• “If that's a blocker, we can…”
• The buyer restating a promise, such as “So you're saying…” or “We were told…”. This is often the clearest record of it.

For each hit, ask three questions. Did we agree, or did they only ask? Does someone other than the speaker deliver it? Is a named customer waiting? If all three answers are yes, it goes in the register.

Then confirm it in writing. List every commitment in the recap email, with dates, and invite corrections. A buyer who replies “actually, we need that before March” has just fixed your register for you.

Automating capture

Manual review works when one person can read every relevant call. Past that point, BuildBetter is one way to automate the capture step.

Its Signals page says it detects 35+ signal types across calls, tickets, Slack, CRM and surveys, including Decision, Action Item, Risk and Blocker. The page also describes full-text search across transcripts and saved searches with alerts.

Its Follow-ups page describes extracting commitments and tasks after a call and drafting a follow-up that references the specific commitment. Each send is logged against the request it closes.

The Deal Intelligence page describes two more capabilities. You can ask the AI Assistant before a call to surface commitments made in earlier conversations, and Salesforce can be updated with next steps.

Treat any extraction as a proposal. The account owner still decides what counts as a commitment and who owns it.

The weekly commitment review

Run a 15-minute weekly review of open commitments, and read the list by account rather than by team. Reading by team hides the account that is owed four things. Attendees are the account owners, one PM and the CS lead. Work through this agenda:

1. New captures: confirm or reject each one, and assign a delivery owner.
2. Stale captures: escalate anything still in Captured after a week with no owner.
3. Due within 30 days: each owner confirms the row is on track or sets the at-risk flag.
4. Past the customer date: set a new date or decline the commitment. Either way, the account owner tells the customer this week.
5. Delivered but not Closed: name who tells the customer, and when.

As accounts approach renewal, add a pass over everything still open for them. How to catch missed customer commitments before renewal covers that review in detail.

Handing commitments off to delivery

Hand off a commitment by creating the delivery item with the quote, the customer date and the recording link attached. Then have the owner accept it in writing. Use this checklist:

• Create the ticket in Jira or Linear, or add it to the onboarding plan, and reference the register ID.
• Paste the exact quote and the timestamped recording link.
• Include the customer-facing date and the strength.
• Add the account, deal stage and renewal date from Salesforce or HubSpot.
• Write a definition of done in the customer's terms.
• Get the owner to accept or push back within two business days.
• Name who tells the customer when the work is delivered.

For firm product or security commitments on late-stage deals, get the owner's acceptance before the contract is signed. If nobody in product will own it, the rep should not promise it.

Close the loop out loud. For example: “In March you said your security review needed SSO. It's live, and here's how to turn it on.” Customers recognise their own words, and that recognition is the payoff for the whole process.

If you use tooling for this step, the Signals page describes pushing signals to Jira, Linear or Slack. The Follow-ups page describes matching shipped work back to the customers who requested it.

A worked example (hypothetical)

In this hypothetical deal, the register turns three verbal promises into three tracked rows. The one that will not be delivered surfaces in week three instead of at renewal. An AE closes Acme in March after promising three things.

In week one, the AE logs all three from the transcript and lists them in the recap email. Priya replies that the review is in mid-March, so the date moves earlier.

In week three, Sam says the CSV export is not planned this half, so C-102 becomes Declined. The account owner calls Acme that week and agrees a manual workaround.

In week six, onboarding finishes on time. Rachel tells the customer, and the row closes.

Without the register, the story goes differently. Product ships a roadmap containing none of the three promises. The CSM treats SAML as a new request when it comes up in a QBR, and the CSV promise surfaces at renewal. The recording existed the whole time, but nobody searched it for promises.

Rolling it out without a mandate

Roll it out as a habit in one segment, not as a company-wide mandate.

• Start with your largest accounts. The volume is manageable, and the stakes justify the effort.
• Make logging take under a minute. Use one row, in a place the rep already looks.
• Show the list back weekly, by account. A list nobody reads stops being maintained.
• Share the first closed loop internally. Pair the customer's reply with the original quote.

Expect the first month to be incomplete. The gaps show you where capture breaks.

Where the register should live: options compared

Start the register wherever your team already works, and move it into tooling once capture or closing the loop starts slipping. This is not a ranking. The table compares where each option needs manual effort.

Common mistakes

The most common mistake is mixing requests with commitments. Most of the others follow from weak ownership.

• Logging requests as commitments. The result is a list nobody trusts, and an untrusted list does not get read.
• Letting the summary replace the quote. Without the original wording, you cannot tell whether you delivered the promise or only something near it.
• Having no Declined status. Unmarked items stay open forever and then surface at renewal.
• Relying on the rep who made the promise. Reps change accounts and leave, and their memory leaves with them.

Frequently asked questions

The short version: the account owner owns the register, every row has a named delivery owner, and anything not written down with a customer and a date is not being tracked.

Who should own commitment tracking?

The account owner owns the list, and each commitment has its own delivery owner. Do not hand the whole thing to sales ops as a reporting exercise, or it becomes a report nobody acts on.

How do you make sure promises made on sales calls actually get built?

Get a named delivery owner to accept each firm commitment before signature. Then track it by customer until it is delivered and the customer is told, or until it is declined and the customer is told.

Isn't this what the CRM is for?

A CRM tracks the deal, not the promises made to win it. A custom object in Salesforce or HubSpot can work, but only if you also solve two things: capture, and linking each row back to the call.

What about commitments made over email or Slack?

The same rules apply: log the quote, the owner and the date. Email at least leaves a searchable trail, which is why calls need the most attention.

How far back should we backfill?

Start today, then backfill open commitments on your largest accounts only. A complete history of small accounts is rarely worth the effort.

What if we decide not to honour a commitment?

Mark it Declined and have the account owner tell the customer immediately. The damage depends mostly on how late the customer finds out.

Sources and further reading

Product claims in this article come from the vendor pages below. The other links are background reading.

• Deal Intelligence use case page
• Signals product page
• Follow-ups product page
• Tasks product page
• Atlassian: Product requirements documents, downsized
• Harvard Business Review: The One Number You Need to Grow

Next step: copy the template above and log the commitments from your last three late-stage calls this week. If you want to see commitment capture run against your own recordings, book a BuildBetter demo and bring one recent deal.