Library · MIDs · Guide
Descriptor phone / URL — claim map
GuideDescriptor phone / URL — claim mapBack to article
Working CS path on the statement line. Dead numbers still file. Distinct from DBA checklist and soft-vs-hard.
| Claim | Reality | Do | Do not |
|---|---|---|---|
| Correct DBA is enough — phone can be dead | No. Cardholders call the printed number first | Test the number answers as this DBA | Ship a voicemail black hole |
| Any marketing URL is fine | No. Expired UTMs and 404s lose the call | Stable page that names the charge + CS path | Print a campaign link that dies next week |
| IVR for a different brand is OK | No. Wrong-brand answer still looks like fraud | Same DBA greeting on phone and site | Park competitor support on your line |
| Changing only the phone skips alert remap | No. String change still stales seats that key the line | Same-day remap on the re-enroll sheet | Leave Ethoca on the old phone fragment |
| This map is the DBA vs LLC checklist | No. Billing-descriptor is what name to print. This map is phone/URL | N/A — open billing-descriptor for DBA rules | Skip the working path because the DBA is right |
| This map is soft vs hard mechanics | No. Soft-vs-hard is how the string is set. This map is contact path | N/A — open descriptor-soft-vs-hard for that fork | Confuse contact rules with soft/hard approval |
Filter the claim. The phone or URL next to the DBA must reach CS who knows that brand. Dead or wrong-brand paths still become unrecognized disputes.
Pairing procedure: Put a working phone or URL on the descriptor. Topic: MIDs.
Work with us — We run this job on your accounts. Services