Trade show follow-up call scripts for resources, demos, and quotes

Start from the promise made at the booth

A trade show follow-up call should refer to the visitor's actual request, check whether now is a suitable time, and agree on one useful next action. Prepare the call from the booth note rather than beginning with a generic sales pitch.

A visitor who requested a technical answer expects a different call from someone who only asked for a document. Before dialing, read the conversation note and identify the promised next step. Check whether a phone call matches the contact route and purpose agreed at the event. If the visitor asked for an email resource and did not request a call, send the agreed resource rather than treating a phone number as an invitation to a different conversation.

A script should keep the purpose clear while allowing the other person to respond naturally. It is a guide for the employee, not a paragraph to deliver without interruption. Prepare a brief opening, one relevant question, and a clear closing action. The call should leave both people knowing what happens next, even when the visitor has no further interest.

A short preparation note before dialing

Confirm the person's name, company, event, question, resource already sent, and open commitment. Check whether another colleague has contacted them so the team does not restart the same conversation. If the record is unclear, resolve the uncertainty internally or begin with an honest clarification. Do not build the script around a guessed budget or buying timetable.

Keep this preparation beside the lead so the outcome can be added to the same context afterward.

Introduce the context and ask about timing

Example opening: Hello [name], this is [caller] from [company]. We spoke at [event] about [specific question]. You asked us to follow up about [agreed topic]. Is now a suitable moment, or would another time be better? This tells the recipient why the call is relevant and gives them a real opportunity to defer it. Use the event and question rather than a vague claim that they expressed strong interest.

If the person is busy, ask whether they want a brief email instead or a time they prefer for the agreed conversation. Do not continue with the pitch after they have said now is unsuitable. Record the arrangement and end politely. If you reached the wrong person, check the appropriate route without sharing another visitor's detailed notes.

Script for a requested resource

Example: At the booth, you asked for [resource] to help with [question]. I sent it on [date]. I wanted to check whether it reached the right address and whether there is one point we should clarify. If it has not arrived, first resolve delivery. If the person has not read it, offer to leave the material with them rather than asking them to review it while you remain on the phone.

If they have read it, ask which question remains. A useful answer may be a single additional page or a short specialist explanation. Do not automatically turn a document request into a long demonstration. Close with the specific item you will send and the person responsible. If there is no remaining question, acknowledge that and avoid inventing a reason for another call.

Script for a demonstration request

Example: You mentioned that you wanted to see how [workflow] would work for [context]. Before we choose a time, which part would be most useful to cover, and should another colleague join? This gives the demonstration a purpose and helps select the right presenter. Offer genuine time options only after the relevant host's availability is checked.

Repeat the accepted purpose, participants, duration, and next confirmation step. A call that ends with send me some times is still a scheduling task, not a booked meeting. Record who will propose those times and when. If the request has changed, update the note so the presenter does not prepare the original scenario after the visitor has asked for a different one.

Script for a quote or commercial discussion

Example: At [event], you asked about a quote for [stated scope]. I would like to confirm the assumptions before the appropriate colleague prepares it. Is [known scope] still correct, and which details remain open? Ask only for information needed to answer the request. If scope is unclear, say what you need to check rather than quoting a price based on guessed requirements.

Do not promise a discount, delivery date, technical capability, or approval that you cannot confirm. A useful next action may be sending the agreed scope to the responsible person and returning with a clear answer. In the note, separate the visitor's requested conditions from your team's accepted commitments. That distinction prevents a preliminary question from being mistaken for an agreed commercial term.

Respond when the visitor's priority has changed

A person may no longer need the resource, may have moved the project, or may prefer to involve another colleague. Ask what changed only if they are willing to explain. The aim is to update the record, not to challenge their decision. If they do not want further contact, record that direction and stop the planned sequence. Do not relabel a clear stop as a temporary objection requiring more calls.

For a later review, ask whether they actually want a future contact and what timing or event would make it useful. Example: Would you prefer that we leave this here, or would a check-in after [agreed condition] help? A vague maybe next quarter should remain tentative until the person agrees on a concrete next action. Preserve the uncertainty so another staff member does not read it as a firm appointment.

Handle an unanswered call without creating a chase

If you leave a message, identify yourself, the event context, and a simple way to respond. Avoid describing sensitive project details in a voicemail you cannot verify. Example: This is [name] from [company], following up on your question at [event]. You can reply to our earlier message when convenient. A voicemail is an attempted contact, not a completed conversation.

Check your team's agreed follow-up plan before another attempt. Repeated dialing by several colleagues creates confusion without adding useful information. Record the attempt and any delivery issue, then decide whether a relevant email, a different agreed time, or no further action is appropriate. The absence of an answer does not tell you the person's buying intent.

Record the outcome and next action in BoothCatch

Make the call through your team's normal phone process. In BoothCatch, update the lead note with what was actually discussed, assign the next owner, and replace the next action with the new commitment. Keep the follow-up status consistent with the work done. A delivered document and an unanswered call are different outcomes, even if both occurred on the same day.

A compact outcome format is: Contact on [date]. Discussed [question]. Outcome [resource received, meeting timing pending, answer required, or no further contact requested]. Next action [task]. Owner [name]. Timing [agreed value or pending]. Record enough for the next colleague to continue without repeating the opening. Avoid speculative notes about mood or interest when a factual outcome is available.

End the call with a shared understanding

Read back the next step in one sentence and ask whether it matches the recipient's expectation. If nothing further is needed, close clearly and update the record. If a specialist must answer, tell the visitor who owns that response and when you can realistically confirm progress. This final check makes the call useful without adding a second pitch at the end.

• The call follows the agreed purpose and contact route.
• The opening recalls a specific booth question.
• The recipient can choose another time or decline.
• The caller asks one relevant question.
• Unconfirmed scope and timing remain explicit.
• The outcome, next action, and owner are recorded.

Frequently asked questions