Setup checklist: make the destination recognizable
Use a name and visual treatment that clients can connect to your agency. ManyRequests documents portal branding and custom-domain use. Explain the intended destination in your normal client onboarding rather than sending an unexplained login link. A branded address can reduce confusion, but it is not proof of who is signed in or what they may access. Keep appearance and security as separate acceptance checks.
Test the actual client route
From a non-sensitive test account, open the invitation, identify the expected organization and locate the next task. Check the narrow-screen experience as well as desktop. A client should not need your internal vocabulary to understand where files and approvals belong. Verify both light and dark branding variants where applicable, and make sure a logo or color change has not hidden an important label or made an action unreadable.
Keep operational messages consistent
The portal name, invitation wording and service instructions should describe the same relationship. If a client pays one business but receives an unexplained invitation from another name, pause and clarify the presentation. Do not imply that a white-labelled portal is software your agency independently developed. Likewise, do not use a merchant’s logo as your own endorsement badge unless you have permission. Clear authorship is more valuable than making every supplier invisible.
Retain a safe fallback
Document the supported access route and a way for the client to report difficulty without sharing passwords. Before changing a domain, understand which invitations and bookmarks may still be in use. Keep the old route available where the provider supports it, and verify the actual migration before broad announcements. This guide does not prescribe DNS changes or claim every custom-domain arrangement works identically; use the current vendor instructions for the configuration you own.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- ManyRequests portal customization — indexing wording conflict — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19
- ManyRequests client experience — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19
- ManyRequests security statements — not independent certification — Merchant documentation · manyrequests.com · Merchant-controlled · checked 2026-09-19