This article explains what data is sent from CallHub to Raiser’s Edge for different campaign types. The system records all the sync back activity as Actions in Raiser’s Edge.
Data Sync back format for different campaigns
Text Broadcasting (Inbound Message)
Connected via <campaign_name> campaign
Message Type: Inbound
Campaign name: <campaign_name>
Message Received: "Hey, I am good"
Source: CallHub
Date: Sep 11 2025, 09 AM LMT
P2P/Call Center Campaigns (Inbound Message)
Connected via <campaign_name> campaign
Message Type: Inbound
Campaign name: <campaign_name>
Message Received: "Hey happy to connect"
Assigned Agent: <agent_username> (<agent first name> <agent last name>)
Source: CallHub
Date: Sep 11 2025, 09 AM LMT
P2P Campaigns (Survey Responses)
Connected via <campaign_name> campaign
Campaign name: <campaign_name>
Assigned Agent: <agent_username> (<agent first name> <agent last name>)
Source: CallHub
Date: Sep 11 2025, 09 AM LMT
Survey Response:
Q: ABC test?
A: c; b; a (semi-colon separated)
Call Center Campaign (Survey Responses)
Connected via <campaign_name> campaign
Campaign name: <campaign_name>
Assigned Agent: <agent_username> (<agent first name> <agent last name>)
Disposition: MEANINGFUL_INTERACTION
Notes: Notes Marked outcome of call
Source: CallHub
Date: Sep 11 2025, 09 AM LMT
Survey Response:
Q: Hey, how are you?
A: I am good
Q: Are you joining the campaign?
A: yes sure
Q: How are you?
A: OptionA; OptionB; OptionC (semi-colon separated)
Below is a table showing what data points are synced to Raiser's Edge NXT from CallHub for different campaign types.
Data Field |
Call Campaign (CC) |
P2P Messaging |
Text Broadcast (TB) |
|---|---|---|---|
Activity Type (Action) |
Phone Call |
Message Activity |
Message Activity |
Campaign Name |
✓ |
✓ |
✓ |
Date & Time |
✓ |
✓ |
✓ |
Source |
CallHub |
CallHub |
CallHub |
Assigned Agent |
✓ |
✓ |
✗ |
Agent Username & Name |
✓ |
✓ |
✗ |
Direction (Inbound/Outbound) |
✓ |
✗ |
✗ |
Message Type (Inbound/Outbound) |
✗ |
✓ |
✓ |
Message Content |
✗ |
✓ |
✓ |
Call Start & End Time |
✓ |
✗ |
✗ |
Call Summary |
✓ |
✗ |
✗ |
Disposition (Call Outcome) |
✓ |
Limited |
✗ |
Notes (Agent Notes) |
✓ |
Limited |
✗ |
Survey Responses |
✓ |
✓ |
✗ |
Survey Format (Q&A) |
✓ |
✓ |
✗ |
Multiple Answers Support |
✓ (semicolon-separated) |
✓ (semicolon-separated) |
✗ |
Attachments (Recording Link) |
✓ |
✗ |
✗ |
Completion Status |
✓ |
✗ |
✗ |
Handling Opt-out Preferences for Constituents during Data sync
When a contact is imported into CallHub and later marked as Do Not Call (DNC) or Do Not Text (DNT), their updated communication preferences are automatically synced back to Raiser’s Edge to ensure both systems stay aligned.
These updates are recorded as Consent in Raiser’s Edge, which is used to manage how a constituent prefers to be contacted across different channels.
For Do Not Call (DNC) – the contact’s Phone consent in Raiser’s Edge will be set to Opt-out, indicating that the constituent should no longer be contacted via phone calls.
For Do Not Text (DNT) – the contact’s SMS consent in Raiser’s Edge will be set to Opt-out in their profile, ensuring that they do not receive text messages going forward.
Have any questions or suggestions? Reach out to us at support@callhub.io or create a ticket from the Support Center.
Comments
0 comments
Please sign in to leave a comment.