Integration evaluation guide
Map a CRM or booking workflow, its supported actions and its failure handling.
Illustrative evaluation sequences, not proof of an active connector. A request and a confirmed booking are different outcomes.
Make call context useful to your team.
Evaluate how the source and outcome information available in your Pulse setup could fit your CRM process.
- Available call fields
- Mapping to review
- CRM record
- Call context
- Which source and campaign fields are available?
- Matching
- How is a call associated with the right record?
- Updates
- Which objects and fields can this setup write?
- Recovery
- What happens when a write fails or is duplicated?
Questions to confirm for Pulse
- Confirm the supported product, plan and connector.
- Define the allowed fields, permissions and data owner.
- Test success, duplicates, errors and recovery.
- Agree on how to disable access when it is no longer needed.
Separate the call, the request and the booking.
Evaluate a calling or Voice AI workflow alongside the CRM and scheduling tools your team already uses.
- Defined call outcome
- Next action to review
- CRM or calendar
- CRM actions
- Which records can the selected workflow read or update?
- Scheduling
- Which calendar or event type is supported?
- Exceptions
- How are unavailable times and failed actions handled?
- Request and booking status
- How are a request, a confirmed booking, and a reschedule represented separately?
Questions to confirm for Signal
- Confirm the supported product, plan and connector.
- Define the allowed fields, permissions and data owner.
- Test success, duplicates, errors and recovery.
- Agree on how to disable access when it is no longer needed.