Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Journey types, structured intake and public applications

Complete Service required

Name the one-off service. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: Service delivery staff, compliance managers, administrators, linked client contacts and public applicantsPermission: Create staff or public visitorModule v1.0.0
Jump to steps
Where to goService Journeys form → One-Off Services
Before you start
  • Verify 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 you’ll accomplish

Name the one-off service. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

  1. Go to Service Journeys form → One-Off Services.
  2. Go to the One-Off Services intake section containing Service required.
  3. Enter or select Service required using the supported value described below.
  4. Continue to the next step or save the current brief so autosave records the value.
  5. Reopen the brief or review page and confirm the value is shown correctly.

Fields and options to review

Service requiredName the one-off service.

Rules the system enforces

  • The field is stored as part of the current request or intake answer set.
  • Leave an optional field blank only when the form permits it; required fields must pass server-side validation.

How to confirm it worked

  • The complete service required 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.
Complete Preferred start dateComplete Authority or third partyJourney types, structured intake and public applicationsBrowse all Service Journeys guidesProjects, tasks and time trackingClient portal overviewCreate a taskUpload and share customer filesConfigure SMTP email deliveryReview email delivery issues