Someone fills out a form, asks about a solution, and days later receives a call that starts from scratch. The salesperson does not know what content they viewed, what they explained, or what response they expected. For an SMB, handing off a prospect from marketing to sales requires a simple protocol that preserves context and makes it clear who should handle it.
The starting point is agreeing on what information sales needs to have a useful first conversation. Marketing will not always have all the answers, but it can distinguish between confirmed information, pending questions, and expectations expressed by the interested person.
1. Define when the contact should be handed off
Agree on which requests will be passed to sales. For example, a demo request, an inquiry about a specific service, or a business need that requires reviewing scope. Downloading informational material may represent a different intent; the team must define how to handle each case without assuming that everyone is looking to buy immediately.
Document these criteria in language that both teams understand. A short list of situations and examples is usually enough to get started. Include what to do when the request concerns support, a job opening, or a supplier, so the contact reaches the right person.
2. Prepare a minimum handoff record
The record should allow sales to understand why it is receiving the prospect. Use information obtained during the interaction and preserve the reference to the form or conversation when available. Record the source with the level of certainty you have; if you do not know the exact campaign, avoid filling it in based on intuition.
- Identidad: nombre, empresa cuando aplique y medio de contacto proporcionado.
- Origen: formulario, evento, contenido o conversación que generó la solicitud.
- Necesidad: qué busca resolver y qué pidió recibir.
- Antecedentes: información ya compartida y preguntas que siguen abiertas.
- Expectativa: canal o momento de contacto que la persona indicó.
- Responsable propuesto: quién recibirá el caso y por qué corresponde a su ámbito.
3. Distinguish sending from acceptance
Sending a list or tagging a salesperson leaves an important part pending: confirming that someone has taken responsibility for handling it. Establish a receipt signal that can be reviewed, such as a recorded activity or a task with an owner. Each company can set an internal timeframe suited to its schedule and capacity; it does not need to be presented as a promise to the customer.
The recipient should check whether they can contact the prospect and whether they have enough context to begin. When the request changes owners, document the reassignment. This prevents marketing from interpreting the handoff as work completed while sales assumes someone else took it.
4. Agree on how to return an incomplete handoff
The return needs a specific reason and a next action. “It doesn't work” offers little information. “A valid contact method is missing” or “the request concerns a service we do not provide” makes it possible to decide whether to correct, redirect or close the case. Define who will resolve the missing information and how they will indicate that the record is ready.
It is also useful to allow acceptance with pending items. A salesperson can start the conversation even without knowing the project size, as long as they understand the request and have a legitimate way to respond. Requesting too much data from marketing can delay a conversation that already makes business sense.
Hypothetical example: a training request
Suppose a training company receives a form from an SMB interested in training its customer service team. Marketing records that there are approximately twelve participants, that they asked about remote sessions, and that they requested contact by email. It adds the material already shared and clarifies that the available dates are still unknown.
Sales accepts the handoff and prepares a first message that revisits those needs. If it discovers that the required service is in person in a city without coverage, it records that reason so marketing can adjust the campaign information. The sales conversation thus leaves verifiable learning for the next case.
Review the protocol with real cases
At first, review a small sample of handoffs with both teams. Look for repeated questions, contacts without an owner, and returns without an explanation. Adjust the format when you find a recurring problem. The protocol should help with the conversation with the prospect, so it is best to remove fields that no one uses to make a decision.
In Onix Board, Audience includes features for managing contacts, tags, segments, histories, conversations, and forms. Team includes tasks and owners. You can evaluate these features to organize an explicit handoff protocol, according to the way marketing and sales work.
Checklist for a handoff ready to handle
- La solicitud comercial está identificada.
- El contacto y sus antecedentes están disponibles.
- Hay una persona que confirmó la recepción.
- Los datos faltantes tienen una acción siguiente.
If you are reviewing how your prospects move from marketing to sales, request a demo and tell us about your process to learn about the Onix Board features you can evaluate: https://onixboard.com/contact