IMPLEMENTATION GUIDE
Use your customer system for account identity
Resolve the sender to an account through your existing support or customer records. A work email domain alone should not establish access to a customer’s tickets or account data. Enrich the known account’s domain to add firmographics after that association is established.
Keep service rules grounded in your own records
Your ticket severity, support plan, and contractual response targets should determine urgency. Employee count provides company context rather than a support entitlement. Display useful fields as an account summary so agents can ask about team rollout or deployment scope instead of assuming the company’s size describes the reported problem.
Reuse the company summary across tickets
Store the completed profile on the customer account and join it to tickets, rather than initiating a lookup for every message. Keep the task ID and timestamps with the summary. Your helpdesk handles queue assignment, account-owner notifications, and responses according to its own workflow.
Connect the workflow
Use the API overview for request and task handling, or the Loop guide for webhook delivery.
Company enrichmentAdd firmographic context to known customer accounts.Common questions
Does EnrichLoops prioritize or answer support tickets?
No. EnrichLoops supplies company data. Your helpdesk and support rules control ticket handling, assignment, and replies.
Should larger companies automatically receive higher priority?
Use ticket severity and your existing support entitlements for priority. Company size can add context, but it does not establish a support obligation or the impact of a problem.