Match the next step to the request
Use a meeting path when a buyer wants to speak with sales, a human-help path when the conversation needs a person, and a purchase destination when that is an approved part of your workflow. Availability depends on your team’s setup and the destination. For example, a fictional software buyer explores reporting, then asks to discuss the team’s requirements with sales. Hobbes can direct the buyer to the approved next step. The team verifies that the scheduling destination supports the intended meeting.Verify the actual outcome
Check the experience before launch
- Agree on the next step your team wants to offer.
- Test the destination and confirm that it belongs to the intended workflow.
- Check a conversation where the buyer accepts and one where the buyer declines.
- Verify the resulting meeting, human request, or purchase at its destination.
Summary
Offer a next step that fits the buyer’s request and your team’s workflow. Measure completion at the destination instead of treating every link click as a business outcome.Related docs
- Prepare relevant follow-up. Sales handoffs
- Keep funnel measures distinct. Funnel metrics
- Continue an evaluation after a meeting. Sales leave-behinds
- Sign in for the detailed setup and verification guide. Verify bookings and handoffs