Ingest failure causes
Store the authoritative failure reason for failed/missed/declined/cancelled outcomes.
Exact navigationVoice gateway → xConnect signed event callback
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
Store the authoritative failure reason for failed/missed/declined/cancelled outcomes. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Open Voice gateway → xConnect signed event callback.
- Locate the record, setting or action used to ingest failure causes.
- Complete the displayed fields or controls exactly as described in this guide.
- Select the available save, submit, update, call, sign, upload or confirm action.
- Return to the related register, portal, dashboard or call panel and verify the recorded result.
Fields, choices and supported possibilities
Event bridge ruleStore the authoritative failure reason for failed/missed/declined/cancelled outcomes.
Code-backed validations and workflow rules
- The endpoint is machine-to-machine, signed, no-store and not a user login API.
Expected result and verification
- The ingest failure causes workflow completes without a validation, permission or availability error.
- The relevant case, document, proposal, call, extension, widget session, timeline or audit evidence shows the expected state.
- Any client-visible or public result appears only where the code explicitly allows it.
Security, privacy and operational checks
- Use a controlled test case, contact, extension or website origin before production rollout.
- Grant the minimum permissions needed and protect private documents, call metadata, signing evidence, API credentials and infrastructure paths.