FROM VISITOR QUESTION TO RESPONSIBLE FOLLOW-UP
Give a website inquiry a clear next step inside the business
Connect useful public explanations with a contact route, an inquiry record and a responsible follow-up, instead of leaving the response in an isolated inbox.
Design the journey around a real question
A visitor needs to understand the offer before deciding whether to get in touch. Tsumira lets the company connect a useful explanation with a supported contact form, quotation route or booking destination where configured. The operational value comes from keeping the resulting request understandable for the team. A form submission is evidence of a question, not proof of a qualified deal or an automatic sale.
Keep the inquiry’s original context
The website inquiry record retains submitted details such as name, reachable contact information, message and page context, with supported fields for topic and preferred date. That gives the responding person a starting point beyond an unexplained email address. Ask only for information that helps the next response. A preferred date in a contact request is a preference; it should not be presented as a confirmed appointment unless the visitor completed the actual booking flow.
- Contact and message context
- Originating page retained
- Preference distinguished from booking
Track a practical response status
The inquiry workspace supports new, read, replied and spam handling, with recorded read or reply timestamps in the relevant status flow. Use these states to coordinate attention and distinguish an unanswered question from a handled request. The status is an operational record, so people should update it consistently with the actual communication. Marking a request replied is not itself evidence that an outbound delivery reached the customer.
- New and handled requests distinguished
- Read and reply timestamps
- Spam kept out of normal attention
Bring the request into customer work
Supported inquiry handling can link the request to CRM contact context through the relevant processing flow. Ambiguous identity and spam must not be treated as permission to merge unrelated people. Once the team understands the request, it can choose the next suitable action: clarify the question, prepare an offer, arrange a real booking or create delivery work. The connection supports that decision without guaranteeing that every submission automatically produces every downstream record.
- Supported CRM contact linking
- Careful identity handling
- A deliberate next action
A concrete workflow
Explain the offer
Make the page answer a specific visitor question and show a relevant contact route.
Receive the request
Retain the message, submitted details and originating page.
Review and respond
Identify the responsible person and update the request status appropriately.
Continue the relationship
Use the actual customer context to choose quotation, appointment or project work.
An illustrative working example
Example: a visitor asks about a site visit
The visitor reads a service explanation and submits a question with a preferred date. The team sees the message and source page, checks the customer context and answers the practical questions. Only after confirming availability does it direct the visitor into the configured booking process. The inquiry status reflects the actual response, while the eventual appointment remains a separate, verifiable record.
Questions about this topic
Does a preferred date reserve an appointment?
No. A date preference in an inquiry is different from completing a supported booking with actual availability and confirmation.
Does every inquiry become a deal automatically?
No. Contact linking and operational review help the team decide the next step. A submission alone does not establish a qualified opportunity.
Can the team distinguish unread and answered requests?
The supported status flow distinguishes new, read, replied and spam, with relevant timestamps for handling.
Does a replied status prove email delivery?
No. It records handling status. Actual outbound delivery has its own evidence and should be checked where it matters.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
HubSpot
Workflow concept: Compare an inquiry’s original question with the externally maintained lead context before follow-up.
Slack
Workflow concept: Assign responsibility for a new website inquiry without treating a notification as a completed reply.
Calendly
Workflow concept: Offer a separate scheduling route after clarifying the inquiry, keeping preference and booking distinct.