Skip to content
SundAIFree call20 min
Menu
Browse all guides

How to move enquiries from email to your CRM without duplicate cases

Give each enquiry one case and one owner. A customer who emails twice may need one reply or two separate jobs. Here is how to tell the difference.

Start with what the customer asked for

A consultancy receives a quote request on Monday. On Tuesday the buyer adds a floor plan. On Wednesday the same buyer asks about a different building. The team needs one contact and two cases. Map what the receptionist uses to tell them apart. A job reference, site address and open case number are good starting points. Write down which information the next colleague actually needs to start work.

Define when to create, update or ask

Identify an already processed message before creating a record. A message identifier can help recognise a repeat delivery. A reply linked to a known case can append a note. A new request from an existing contact can open a separate case. HubSpot uses email to identify contacts in common creation flows. The sender’s address alone cannot tell your team which job a message concerns. If two cases match, ask a colleague to choose.

Hand the work to a named person

Make the next action visible in the CRM. For a quote request, record who prepares it and when the customer expects an answer. Send ambiguous requests to a queue owned by a named team member. During the pilot, keep customer replies in draft and compare incoming requests with assigned cases at the end of each day.

Sources