Description
Preserve an explicit emergency-contact response-channel preference.
Defensive administrative records connect notices, approvals, owners, policy versions and declared clock conventions. A signed-off label or an active-owner flag describes supplied records rather than granting access or authenticating a control. Clock offsets require an explicit sign and common epoch before timestamps can be compared as an ordered log.
Preserve an explicit emergency-contact response-channel preference.
When to use this tool
Use Emergency Contact Response Channel Label when you already have contactRecordId, suppliedResponseChannel, preferenceSource and need to preserve an explicit emergency-contact response-channel preference.
How to use the tool and how it works
- Enter contactRecordId, suppliedResponseChannel, preferenceSource. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter contactRecordId, suppliedResponseChannel, preferenceSource using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| contactRecordId | Contact Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| suppliedResponseChannel | Supplied Response Channel | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| preferenceSource | Preference Source | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"contactRecordId": "C17",
"suppliedResponseChannel": "phone",
"preferenceSource": "Contact form"
},
"output": {
"token": "[\"C17\",\"phone\",\"Contact form\"]"
}
}Limitations and assumptions
- The result records supplied values without contacting anyone. Sources and asserted relationships are not independently authenticated.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Check original notices, controlled policy versions and current role records when assessing authorship or ownership. For event ordering, reconcile documented clock offsets and timestamp precision against the original logs; this helper does not authenticate or synchronize them.
References
Similar or alternative tools
- Continuity Role Primary Deputy Label
Pair explicit primary and deputy continuity-role identifiers.
- Permission Review Approver Sign Off Tag
Preserve an explicit permission-review sign-off reference.