Start with a request, not just a contact.
One person can ask for a demo twice. A delivery retry can send the same request twenty times. Those are different situations. QualiRelay’s intake contract uses a stable source event ID to keep legitimate inquiries separate from repeated deliveries.
The initial integration requires a customer-controlled backend or supported form service with durable submission storage and signed server-to-server delivery. Source retries and a monitored fallback are verified before live activation.
Read existing evidence before buying more.
Resolve permitted company and contact context from the connected HubSpot portal. Keep the source, freshness, and uncertainty of each material fact. Missing job title, conflicting company matches, or stale data stay visible.
Qualification uses explicit, versioned rules. A score can be 65–85 out of 100, partial. It is not a conversion probability. Optional model assistance supports bounded normalization and explanations; it cannot choose the final owner or authorize a purchase. Optional supplier data requires separate rights and budget approval.
Preserve the relationship. Name the next owner.
A valid existing account owner takes precedence. Otherwise, an approved rule selects an eligible distribution team or an accountable fallback. Every tier has one active policy; Starter supports one distributing team, while Pro and Scale support multiple teams within that policy.
The application records its responsible owner. Default CRM writeback is limited to approved application-specific fields; the standard HubSpot owner is preserved.
Separate the stages of follow-up.
- Assignment: a representative or approved coordinator is accountable.
- Notification: delivery to the approved destination is confirmed.
- Acknowledgement: an authorized person accepts responsibility.
- Response evidence: a qualifying CRM activity or clearly labeled manual attestation is recorded.
A Slack reaction is not prospect contact. Missing CRM logging is not proof that nobody replied. The application keeps notification failures, incomplete telemetry, and overdue evidence distinct.
Review before activation.
Test representative synthetic or customer-authorized examples. Compare the proposed policy with expected outcomes, inspect disagreements, and approve the exact version. Shadow observation evaluates current traffic without production workflow writes or paid workflow decisions.
Assisted onboarding verifies sources, mappings, working hours, fallback, supported permissions, and regional requirements. Live trials and paid pilots start at approved activation, after readiness. Production-account verification remains a separate step from this local implementation.
A focused first configuration.
One HubSpot portal, one Slack workspace, and signed intake sources per workspace. No native outbound email engine, prospect database, calendar scheduler, autonomous SDR, or Salesforce integration is included.
If your existing HubSpot workflows already give you clear ownership and sufficient follow-up visibility, native tooling may be enough.