Britixo CRMBritixo CRM Enterprise Help Centre
Help centreClient Discovery & Project Briefing PortalUnderstand customer and contact matching
Public intake and Companies House assistance

Understand customer and contact matching

The model attempts to create or link a CRM customer/contact for the public visitor.

Audience: CRM administrators, project teams, developers, authorised client contacts and public prospectsPermission: Public visitorModule v1.1.1
Exact navigationPublic discovery submission
Before you begin
  • Confirm the module is active and use the exact navigation shown above.
  • Use an account with the stated module and core CRM permissions.
  • Use known test records when changing statuses, visibility, saved filters or global navigation.

What this guide covers

The model attempts to create or link a CRM customer/contact for the public visitor. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Open Public discovery submission.
  2. Locate the record, endpoint, field or action used to understand customer and contact matching.
  3. Complete the displayed values exactly as described in this guide.
  4. Select the available save, submit, send, upload, create, update or confirm action.
  5. Return to the related register, portal, activity log or API response and verify the expected result.

Fields, choices and supported possibilities

Workspace or endpointPublic discovery submission
PurposeThe model attempts to create or link a CRM customer/contact for the public visitor.

Code-backed validations and workflow rules

  • The action is available only where the supplied module exposes it and the signed-in user or API client meets the stated access conditions.
  • Internal helpers are documented under the visible workflow or endpoint they support rather than presented as invented menu pages.

Expected result and verification

  • The understand customer and contact matching workflow completes without a validation, permission, ownership or availability error.
  • The related record, portal view, activity entry, notification log or API response shows the expected state.
  • Client-visible, public and API data remains limited to the code-backed ownership and visibility rules.

Security, privacy and operational checks

  • Use controlled test records and non-production credentials before wider rollout.
  • Grant least privilege and protect secure links, personal data, uploaded files, signatures, API tokens, allowed origins and server IPs.
Understand public intake validationCreate the public visitor requestPublic intake and Companies House assistanceBrowse all Client Discovery & Project Briefing Portal guidesClient portal overviewAdd and manage customer contactsConfigure customer contact permissionsUpload and share customer filesConfigure SMTP email deliveryReview email delivery issues