CRM INTAKE
Let a genuine inquiry become useful customer context.
Connect supported website inquiries, quote requests and bookings to customer records, while keeping the original interaction available for follow-up.
Please send a proposal for the brand project.
Original enquiry · Website enquiry
The first message should not need a second manual copy
A new inquiry already contains a name, contact details and a reason to talk. Re-entering those facts into a separate customer list adds a handover before the work has begun. Tsumira connects supported intake flows to CRM so the person handling the response can start from the submitted information and its source, rather than an unrelated blank customer record.
Keep the website inquiry and customer linked
For a supported website inquiry, the CRM consumer can recognize or create the contact and add the customer’s words to their activity history. The inquiry retains its connection to that contact. Email and normalized telephone details help recognition. An inquiry already classified as spam is not turned into a customer by this flow. The team can still inspect incoming inquiries in the website workspace and decide what deserves a response.
- Website inquiry-to-contact association
- Inquiry content in customer activity
- Spam-aware processing
Please send a proposal for the brand project.
[email protected]Unclear identity stays available for review.
Retain the origin of a quote request or booking
Quote-request intake can create a sourced opportunity linked to the contact, keeping the request’s origin available to the operator. Booking creation also carries customer details and a contact association. These are distinct business flows with their own validation and enabled-module requirements. A useful intake record tells the next person whether the customer asked a question, submitted a structured quote request or reserved a time, rather than reducing every arrival to the same generic lead.
- Quote request source context
- Booking and contact association
- Flow-specific validation
Handle uncertain identity without a forced match
A supported inquiry or quote request is not attached to an arbitrary person when the available reach data matches multiple contacts. The listener can skip the uncertain CRM association while the original intake remains available for review. Repeated delivery also should not manufacture another customer interaction for the same source event. This helps preserve a readable relationship history without claiming that all real-world identities can be resolved automatically.
- No forced association for ambiguous reach data
- Original inquiry remains reviewable
- Source-aware repeated-delivery handling
A concrete workflow
Publish a supported intake path
Use the configured inquiry, quote-request or booking flow and verify that the required modules and processing are available.
Receive the customer’s information
The source records the submitted identity details and the specific request or appointment.
Review the CRM context
Open the connected contact or opportunity and inspect its source and recorded activity.
Take responsibility for the response
Assign the appropriate owner and document the next step, resolving uncertain matches before relying on them.
An illustrative working example
Illustrative workflow: a website inquiry becomes a follow-up
A visitor asks a consultancy about an upcoming assignment through its website form. The supported processing recognizes an existing contact by their email and records the inquiry in the contact’s activity. The consultant reads the visitor’s question in that context, checks the company association and records a follow-up date. If the email could identify several existing contacts, the team reviews the original inquiry instead of trusting a forced association.
Questions about this topic
Does every external channel always create a customer?
No universal rule is promised. The supported inquiry, quotation, booking and channel-specific flows each have their own requirements and recognition behavior.
What happens to an inquiry marked as spam?
The website-inquiry CRM consumer skips an inquiry already classified as spam, rather than turning that message into a new customer record.
Can an ambiguous email match attach to the wrong person?
The inquiry and quotation listeners explicitly avoid choosing an arbitrary contact when the reach data identifies multiple candidates. Review the source request to resolve the uncertainty.
Is this processing independent of the enabled modules and worker?
No. The relevant modules and background processing must be available. A connected source record is not a promise that every deployment has every channel configured.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Shopify (OAuth)
Workflow concept: Review a customer purchase event before deciding its CRM activity context.
Calendly
Workflow concept: Assess a confirmed appointment as a candidate for the customer activity history.
Gmail
Workflow concept: Match a relevant inquiry to the correct customer before recording its activity.