Skip to main content
Magic Receptionist
Contact Us See plans

Magic Receptionist partner enablement

Learn the relationship you operate. Run the real journey. Know exactly what happens next.

This page is for people selling, referring, or operating Magic Receptionist. Use TEST identities for QA. Real prospects and customers stay in the normal sales and onboarding workflow.

Choose your role Compare partner paths

Role-specific journeys

Do not use one generic Partner workflow for every relationship.

Affiliate

Refer qualified businesses while Aura owns the customer relationship and billing.

Open Affiliate application →

Completion checks

  • □ Explain the difference between Affiliate and Reseller without using commission guesses.
  • □ Submit a TEST Affiliate application and confirm the review state is clear.
  • □ After controlled activation, verify the referral link carries attribution into customer signup.
  • □ Confirm an Affiliate cannot administer a Reseller client portfolio.

Reseller

Sell Magic Receptionist to outside client businesses you own and bill.

Open Reseller application →

Completion checks

  • □ Explain client ownership, support responsibility, branding, and wholesale terms only from the approved account record.
  • □ Submit a TEST Reseller application and confirm it remains in review until explicitly approved.
  • □ Verify approved client provisioning remains scoped to the Reseller portfolio.
  • □ Confirm Reseller accounts do not inherit Affiliate commission or payout behavior.

Sales manager / contractor

Qualify opportunities, help the correct relationship enter the system, and keep next actions visible.

Open Client Services →

Completion checks

  • □ Identify whether an inquiry is a customer, Affiliate, Reseller, Strategic Partner, or multi-location customer.
  • □ Use the correct intake path instead of creating a generic Partner record.
  • □ Keep the prospect, owner, status, and next action visible to the operating team.
  • □ Escalate terms, approvals, and provisioning exceptions instead of inventing an answer.

Customer handoff

The sale is not complete when a form is submitted.

1

Relationship recorded

The customer or partner enters through the correct path and gets the correct review state.

2

Attribution preserved

A valid referral or Reseller relationship survives signup and account creation without being silently replaced.

3

Client provisioned

The resulting customer workspace is created under the correct ownership and tenant boundary.

4

Next action visible

The operator can see status, exceptions, and what needs to happen next without developer access.

QA and escalation

A failed step must be visible and reproducible.

When testing

  • • Use an explicitly approved TEST identity.
  • • Record the role, URL, action, expected result, actual result, and timestamp.
  • • Check mobile and desktop behavior for every critical form and status screen.
  • • Never include passwords, API keys, payment details, or customer-sensitive data in evidence.

When something fails

  • • Do not create a substitute relationship or manually fake attribution.
  • • Keep the application or customer in a truthful recoverable state.
  • • Record the exact failure and route it to the owning issue.
  • • Rerun the failed journey after the fix before calling it complete.