Client intake
Give clients a recognisable place to provide requested documents.
White-label file sharing
Your brand.
A familiar exchange.
Provide a branded exchange experience for customers, suppliers and partners.
Named recipients · Defined access · Recorded activity
MX / CONTROLLED EXCHANGE04
Assemble the approved package.
↗
Client-Onboarding-Documents.zipIllustrative file package
MXTHE EXCHANGE IN CONTEXT
Give the handoff some context.
Customers and suppliers need to recognise the route you ask them to use. A branded exchange can make the intended destination clearer while retaining a controlled file workflow.
MX provides a route for sensitive business files between named recipients. Match access conditions to the purpose of the exchange and use the available activity record to support follow-up. Keep the underlying approval and information-handling decisions in your own process.
WHERE THE WORKFLOW HELPS
The moments that need a handoff.
Supplier delivery
Use an agreed branded route for supplier handoffs.
Partner exchanges
Make the organisation behind the request easy to identify.
A HANDOFF, IN PRACTICE
The right files.
The full context.
A business wants clients to recognise the route used for document exchange. Prepare the branding and domain requirements alongside a clear intake checklist. Walk through the experience as a new client, from the initial instruction to the point where the requested files are ready for the responsible team.
Illustrative workflow · Adapt to your approved process
Design a recognisable client intake
↗Client-Onboarding-Documents.zip
A POSSIBLE PACKAGE
- ✓Requested-document checklist
- ✓Client instructions
- ✓Verified support contact
INTENDED RECIPIENT
The client contact named in the onboarding process
A USEFUL RESULT
The client recognises the intended destination, understands the request and knows where to get help if access fails.
MAKE THE FIRST EXCHANGE COUNT
Test the details.
Then repeat with confidence.
Use the example package as a starting point for a small, representative trial. Agree the success criteria with the person who will actually receive the files.
Check completeness
Requested-document checklist should be easy to identify in the inventory. Open the delivery copy independently of your working folder to catch missing files or local dependencies.
Walk through access
Test with the intended recipient role and receiving environment. Confirm the access conditions, the instructions and the route for getting help.
Agree what success means
The client recognises the intended destination, understands the request and knows where to get help if access fails. Record any remaining questions before making the exchange part of routine work.
FROM PREPARATION TO RECEIPT
Give each exchange
a clear sequence.
Use Client-Onboarding-Documents.zip as an example of a defined package. Replace it with the approved files and instructions for your actual task.
Explore the MX feature set ↗- 01
Confirm the purpose and recipient
Check who is entitled to receive the information. Record the business purpose through your normal approval process before assembling the package.
- 02
Prepare an approved package
Choose the required files, check their versions and remove unrelated information. Include concise instructions so the recipient knows what to do next.
- 03
Apply the access conditions
Confirm authentication, availability and any download conditions for your service. MX's existing features include named access, MFA and configurable expiry controls.
- 04
Review the exchange
Check the recorded activity and follow up through the agreed process. Keep the exchange reference with the project or client record it supports.
DEFINE THE BOUNDARY
Check the fit
before the first file.
Confirm supported branding, domain configuration and plan requirements with MX. Branding should complement verified communication, not replace identity checks.
Assess the controls against a representative package and recipient. Confirm any mandatory capability, contract term or deployment requirement with the MX team before relying on it.
Discuss your exchange requirements ↗PRACTICAL QUESTIONS
What to know
before you begin.
Questions about white-label file sharing and the exchange workflow.
What should the invitation explain?+
State who is requesting the files, why they are needed and how the client can verify the request through a trusted contact. Confirm supported portal and domain configuration with MX before planning the rollout.
Can I use a custom domain?+
MX's existing feature material describes branded portals and custom-domain options. Confirm configuration, ownership checks and availability for the service you plan to use.
How should we prepare the files?+
Give clients a recognisable place to provide requested documents. Check the approved version, any required dependencies and the recipient's ability to use the package. Include only the material needed for the purpose.
What should we verify during a trial?+
Test a representative exchange from sender preparation to recipient access. Check authentication, permissions, expiry behaviour and the activity available afterwards. Include the actual file types and recipient environment you expect to use.
Does an access expiry remove downloaded copies?+
Do not assume expiry deletes a recipient's local copy. Agree post-download handling and retention responsibilities, and confirm the precise behaviour of the service configuration you plan to use.
Where can we check product details and commercial terms?+
Use the current MX product information and confirm the proposed service with the team. Review the plans and pricing alongside your actual users, workflow and deployment requirements.
YOUR NEXT EXCHANGE STARTS HERE
Valuable data.
Better protected.
Put better controls around your next sensitive file exchange. See how MX fits your organisation's workflow.
7 days freeUp to 5 usersNo credit card
- Full feature access
- Unlimited file size transfers
- Named recipients and MFA
- Custom branding and upload portals