Directory, Live now, presence and call history

Call a Live now entry

Select the available call action for the online customer or visitor.

Audience: CRM administrators, staff callers, customer contacts, voice-platform engineers and website operatorsPermission: Use internal callingModule v1.1.3
Exact navigationAdmin Area → top navigation → xConnect phone icon
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

Select the available call action for the online customer or visitor. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Open Admin Area → top navigation → xConnect phone icon.
  2. Locate the record, setting or action used to call a live now entry.
  3. Complete the displayed fields or controls exactly as described in this guide.
  4. Select the available save, submit, update, call, sign, upload or confirm action.
  5. Return to the related register, portal, dashboard or call panel and verify the recorded result.

Fields, choices and supported possibilities

Directory/presence/history actionSelect the available call action for the online customer or visitor.

Code-backed validations and workflow rules

  • Returned records are scoped to the authenticated context and current module settings.

Expected result and verification

  • The call a live now entry 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.