CRM and enquiries
Keep the customer context with the job.
A practical CRM pattern for sign teams: capture the request, clarify the site and owner, and carry the conversation into a reviewable workflow.
Published by Spectra · no named expert reviewer is claimed · last reviewed 17 September 2026 · operational guidance, not technical, legal or safety certification.
The practical answer
A sign-shop CRM earns its place when it makes the next action and the job context easier to find. It should preserve contacts and consent while connecting the enquiry to the actual work being quoted and delivered.
Capture context
A contact is not yet a usable job brief.
For sign work, a useful customer record needs the enquiry source, site, decision-maker, requested outcome and the questions still open. Do not turn a sparse inbound message into a completed specification; show the uncertainty so the next conversation has a clear purpose.
- Organisation, contact and preferred route
- Site or locations connected to the request
- Source, timing and requested work
- Authority and buying-role notes
- Open questions and agreed next action
Keep the conversation attached
Make follow-up a job decision, not a private inbox task.
Link a call note, survey request, quote and proof discussion to the same customer and job context. That makes it easier to hand work between sales, design and operations without claiming that an unqualified conversation has converted.
Use consent honestly
A service enquiry and marketing permission are different things.
A response about a requested demo or resource is distinguished from an optional marketing subscription. The website records those choices separately and does not treat marketing permission as a condition of receiving a response.
Spectra boundary
A website enquiry is not a live CRM integration.
The public form writes only to a dedicated website database and returns a durable receipt. Spectra does not currently claim live lead scoring, email sequences, contact sync or marketing automation.
A sample, not a promise