Why it matters
Channel mappings help route messaging through the right channel when the sender depends on custom data such as a location, branch, office, brand, or other object value.
Key Concepts
Channel mapping: A setting that maps custom data values to Whippy channels.
Custom data type: The object or data type used as the source for the mapping.
Custom property: The property whose values determine which channel should be used.
Mapping definition: A value-to-channel row that tells Whippy which channel to use for a specific data value.
Sequence routing: A common use case where messaging workflows use data to determine the sending channel.
Step-by-Step: Create or review a channel mapping
Open Settings.
Select Channel mappings.
Review existing mappings before creating a new one.
Select Add channel mapping.
Enter a mapping name.
Choose the custom data type and custom property.
Add mapping definitions that connect each value to the correct channel.
Save the mapping and test it with records that contain the mapped values.
Tips and Best Practices
Use clear mapping names that explain the source data and routing purpose.
Confirm the custom property is populated before relying on a mapping.
Review mappings after adding new channels, locations, branches, or brands.
Coordinate with Settings > Objects so the mapped property remains stable.
Troubleshooting
Issue | Possible Cause | Fix |
Messages use the wrong channel | The mapped value does not match the object record value or points to the wrong channel | Review the mapping definitions and test with a known object record |
A value is missing from the mapping | The custom property has new or unexpected values | Add a mapping definition for the missing value |
The custom property is not available | The object definition or property is missing, hidden, or restricted | Review Settings > Objects and confirm the property exists |