Run client work, communications, AI, and business services from one MX12 guide.
This guide explains what is available now, how to complete common client workflows, and what MX12 is preparing next. Use it for accounts, companies, tasks, CRM, AI, websites, domains, support, telephony, virtual numbers, PBX, eSIM, marketplace, and billing.
Four steps are enough for the first session.
Use the email connected to your MX12 account. If you are new, create an account and confirm your email before opening the dashboard.
Make sure your name, contact email, active services, requests, and balance look correct.
Describe what you need, add links or screenshots, choose the best category, and submit the ticket.
Open the request or chat later to read updates, answer questions, and confirm when the issue is solved.
Use one client account for chat, tickets, billing, and updates.
Register
Create your account with a real email address. Use a password that is unique to MX12.
Log in
Enter your email and password. If extra verification is enabled, enter the current code from your authenticator app.
Recover access
If you cannot log in, use password recovery or contact support from the same email used for the account.
Use the right MX12 area for the job.
| You need to | Open this area | Best next action |
|---|---|---|
| Ask a quick question | Chat | Send one clear question and include the page or account detail if it matters. |
| Report a problem | Support requests | Create a ticket with title, screenshot, device, browser, and expected result. |
| Install website chat | Widget settings | Copy the public key, allow your domain, paste the script, and test in incognito. |
| Coordinate company work | Tasks | Create a task with an owner, priority, dates, acceptance details, files, and task chat. |
| Manage contacts and sales | My CRM | Add contacts, create deals, move work through pipeline stages, and keep notes and activity together. |
| Configure the AI assistant | Settings → AI | Add company facts, approved sources, communication style, guardrails, languages, escalation rules, and website widgets. |
| Buy or manage a number | Telephony | Choose a country or offer, complete documents and payment, then wait for activation before connecting calling. |
| Use website calling | Telephony | Connect calling after the number is active. MX12 separates the provider route from the internal webphone extension. |
| Configure team call routing | Telephony → PBX | Create extensions, devices, groups, schedules, voicemail, IVR, forwarding, and inbound rules allowed by your account. |
| Buy travel data | Telephony → eSIM catalog | Choose a country or region, compare data and validity, order once, then install using the private activation details. |
| Search, sell, or rent an offer | Marketplace | Search listings, save useful offers, open listing chat, or publish an offer from a seller or company account. |
| Plan a business website or domain | Business sites roadmap | Review the planned publishing, domain, industry template, managed chat, and custom CRM workflow before requesting early access. |
| Check money or invoices | Billing | Review balance, payments, package status, and receipts before opening a billing ticket. |
| Protect your account | Security settings | Enable authenticator app verification and keep backup access details private. |
Your dashboard is the main place for work with MX12.
Open current tickets, see status, read answers, and add new details.
Continue conversations and check whether AI or a support specialist is handling the thread.
View balance, payments, packages, and invoices connected to your account.
Review contact details and security settings so the account stays reachable and protected.
See the active company workspace, members, roles, shared limits, channels, and services available to your team.
Coordinate internal work with status, priority, dates, assignees, files, and a conversation attached to the task.
Keep contacts, deals, pipeline progress, notes, activities, and follow-up tasks in one business workspace.
Review numbers, eSIM data, call minutes, active services, order status, mobile access, and PBX configuration.
Log in and use the top navigation to open your client dashboard.
Review open requests, unread chat replies, billing balance, and any active package or service.
Create a ticket, continue a chat, update contact details, or check a payment without switching tools.
Keep personal access separate from shared company work.
Your user account identifies you. A company workspace connects the people, tasks, AI settings, channels, CRM data, telephony services, and shared limits that belong to one business. What you can see or change depends on your role.
Use your own email, password, security settings, notification choices, and device sessions. Never share one login between employees.
Create or join a company before using shared tasks, company clients, team channels, CRM, or account-wide AI rules.
Owners and administrators manage company-wide settings. Members work only with the tools and records allowed for their role.
Turn a business request into assigned, trackable work.
The task board is shared inside one company. Use it for client delivery, website work, sales follow-up, telephony setup, content, operations, and internal projects instead of splitting decisions across unrelated chats.
Describe the result
Write a short title and a complete description with context, links, acceptance criteria, and the outcome that means the task is finished.
Assign responsibility
Choose the responsible people, status, priority, start time, and deadline. Use realistic dates that the assignee can understand.
Add files and review
Attach the source files, screenshots, briefs, or examples, review the summary, then create the task.
| Use the task field | For this purpose | Good practice |
|---|---|---|
| Title | Identify one result | Start with an action: “Connect the sales number” or “Publish the restaurant landing page.” |
| Description | Explain context and acceptance | Add links, constraints, expected result, and anything that must not be changed. |
| People | Set responsibility | Assign the person who owns the next action, not everyone who may be interested. |
| Priority and dates | Plan work | Use urgent priority only when delay has a real business consequence. |
| Files | Keep source material together | Attach the current version and name files clearly. |
| Task chat | Keep decisions with the task | Continue updates in the same task so the final history is complete. |
Keep customer context, sales progress, and next actions connected.
My CRM brings together pipeline lanes, contacts, deals, notes, activity, and execution tasks. Use one record per real customer or company and update the existing record instead of creating duplicates.
Review pipeline lanes, recent contacts and deals, quick notes, activity, and the current execution lane.
Store the customer or company name, communication details, context, and the relationship that your team needs.
Create an opportunity, keep its value and stage current, and record the next action required to move it forward.
Connect follow-up work to a responsible person and date rather than relying on memory or private messages.
Use the stream to understand what changed and which customer action happened most recently.
Adjust the CRM options available to your company. Deeper industry templates are part of the planned business-site workflow below.
Create a ticket when you need a clear answer or tracked work.
Write a useful title
Use a short title that names the exact problem or request.
Add context
Include links, screenshots, account email, device, browser, time, and what you already tried.
Send and watch status
After submitting, track the status from the dashboard and answer follow-up questions inside the ticket.
| Status | What it means for you |
|---|---|
| Open | Your request is created and waiting for review. |
| In progress | The team is working on it or waiting for a needed detail. |
| Waiting | MX12 needs your answer before the request can move forward. |
| Done | The request is completed. Reopen or create a new ticket if something else is needed. |
Use chat for quick questions and simple support.
Short messages with one topic get better answers than long mixed requests.
Add the page, order, email, screenshot, or error text that explains the situation.
If the answer is not enough, ask for the conversation to be reviewed by a support specialist.
Give AI approved facts, clear limits, and a reliable human handoff.
Open Settings → AI to configure the company and AI voice, customer script, preferred language, translation behavior, communication style, additional web sources, strict guardrails, website widgets, and knowledge sources. The guided setup chat can improve existing settings, fill gaps, polish tone, tighten limits, start from zero, or help with installation.
Define the company
Add the official company name and website, a factual company description, products and services, audience, locations, hours, contact routes, and the welcome message.
Choose trusted knowledge
Add approved pages, documents, policies, prices, FAQs, and source priorities. Remove old files when the information is no longer valid.
Set rules and escalation
State what AI may answer, what it must never invent, when it must ask a clarifying question, and when it must send the conversation to a person.
| Configuration | What to write | What to avoid |
|---|---|---|
| Company information | Verified facts, services, coverage, contacts, hours, and customer process. | Unconfirmed claims, expired offers, or internal passwords. |
| Communication style | Tone, answer length, preferred terminology, language, and how to address customers. | Vague instructions such as “answer perfectly.” |
| Trusted sources | Official websites, current documents, product catalogs, price pages, and policies. | Unknown sites or sources that may conflict with company policy. |
| Guardrails | Approval limits, privacy rules, prohibited promises, escalation triggers, and sensitive topics. | Rules that allow AI to confirm payments, legal outcomes, or service activation without verification. |
| Human handoff | When to create a request, ask for a manager, or collect the contact details needed for follow-up. | Keeping the customer in a loop when AI cannot complete the request. |
Choose the preferred team language, whether incoming messages are translated, and whether the default view shows original or translated content.
Create a separate widget when a website, storefront, product, client project, or domain group needs different knowledge, appearance, or starter questions.
Review real conversations, correct the source information, and improve rules. Do not fix a wrong answer only by adding more personality text.
Do not add passwords, private keys, payment card data, authentication codes, private customer files, or provider credentials.
AI may explain, collect context, summarize, and suggest next actions. A person must approve financial, legal, security, domain-transfer, and customer-commitment decisions.
Connect the MX12 chat widget to your website.
The widget is the small chat button on your site. It lets visitors ask the AI, continue a conversation, and request human support when the question needs attention.
Open widget settings
From your client dashboard, open the chat or widget area and find your public key.
Add your domain
Make sure the exact website domain is allowed, for example example.com and www.example.com if both are used.
Paste the code
Add the script before the closing </body> tag or through your website builder custom code area.
<script
async
src="https://www.mirrax12.world/static/js/widget-loader.js?v=20260831-permanent-free-plan-v51"
data-version="20260831-permanent-free-plan-v51"
data-public-key="YOUR_PUBLIC_KEY"
data-base-url="https://www.mirrax12.world"
data-ticket-hint="General Support Question">
</script>For WordPress, Shopify, Webflow, Tilda, Wix, or custom HTML, place it in global footer/custom code so it appears on every page that needs chat.
Replace YOUR_PUBLIC_KEY with the key from MX12. Keep data-base-url pointed to MX12.
Open the site in an incognito window, wait for the chat button, send a test message, and confirm the conversation appears in MX12.
Use separate widget keys for different client projects, storefronts, checkout flows, documentation portals, or product areas when they need different rules or knowledge.
Start with the company’s real intake process: required questions, safe answers, lead fields, booking or quote steps, and the exact moment a person should take over.
Allow only the production and approved test domains that should load the key. Disable or regenerate a key if it may have been exposed.
Check the public key, allowed domain, ad blockers, browser console errors, and whether the script is loaded only once.
Create a support request with the page URL, public key, browser console screenshot, and the exact test message time.
Manage virtual numbers, calling, SMS, SIP access, and mobile connectivity.
The telephony area is where you request virtual numbers, eSIM packages, SIP access, webphone and mobile calling. Depending on the country, provider, number type, and account permissions, services may also include SMS, call records, recordings, transcripts, AI analysis, multiple workspaces, and PBX routing. Some services are instant; others require documents, balance, and provider activation.
Choose a service
Select a virtual number, eSIM package, or SIP profile. For numbers, check the country, monthly price, setup price, and any document requirements.
Finish verification
Upload requested documents and keep enough balance for setup and renewal. The dashboard shows when the profile or order needs review.
Activate calling
After the number becomes active, connect calling from the service card. Website calling and app access are prepared automatically when the provider route is ready.
Best for receiving calls in a chosen country, showing one business number, and connecting the number to MX12 calling tools.
Best for mobile data while traveling. Keep the QR or activation details private and open a ticket if activation data is missing.
Best when your team needs browser calling, app calling, or a dedicated calling profile attached to the account.
When the selected number supports messaging, use the shared inbox, open one conversation, send replies, and keep unread status connected to the correct line.
Review recent calls and available details. Recording, transcription, summary, outcome, sentiment, and objections appear only when enabled and permitted.
Accounts with more than one telephony scope must select the correct workspace before ordering, calling, changing policy, or reviewing usage.
Check documents, balance, country requirements, and order status before creating a duplicate request.
Create one ticket with the number, service card screenshot, error text, and time of the attempt. MX12 can re-check the provider route without changing your public number.
Decide who rings, when they ring, and what happens next.
PBX settings control the internal call structure behind active numbers. Availability depends on the company role, provider route, and enabled service. Make one routing change at a time and place a test call before changing the next layer.
| PBX area | Purpose | Check before saving |
|---|---|---|
| Extensions | Create internal team destinations. | Owner, display name, caller ID permission, and expected device. |
| Devices | Connect browser, mobile, or SIP endpoints to an extension. | Use current credentials and revoke devices that should no longer connect. |
| Forwarding | Send calls to another destination under defined conditions. | Destination format, timeout, order, and loop risk. |
| Ring groups | Ring several available team members. | Members, order or strategy, timeout, and fallback. |
| Schedules | Apply business hours and after-hours behavior. | Time zone, working days, holidays, and current open/closed state. |
| Voicemail | Collect a message when nobody answers. | Mailbox owner, greeting, notification route, and retention policy. |
| IVR menus | Let callers choose a department or action. | Prompt audio, key mapping, invalid input, timeout, and fallback. |
| Inbound rules | Connect an incoming number to the correct PBX flow. | Number, provider route, destination, priority, and active schedule. |
| Media and hold | Control approved prompts, greetings, and hold audio. | Audio quality, rights to use the file, volume, and customer experience. |
Do not forward two extensions or external numbers back to each other. A loop can create repeated call attempts and unexpected charges.
Recording and transcription requirements vary by country. Configure consent notices and retention with appropriate legal guidance.
Choose, install, and protect a digital mobile-data plan.
Check the device
Confirm that the exact phone or tablet supports eSIM, is carrier-unlocked, and can add another mobile plan.
Choose coverage
Select a country or region, then compare included data, validity, supported networks, activation conditions, and total price.
Install once
Open the order details, scan the QR code or enter the activation information, label the line, and enable data roaming only when the plan instructions require it.
Install while you have stable Wi-Fi, but follow the package rule for when validity starts. Some plans begin at installation; others begin at first network use.
Select the eSIM for mobile data, keep the primary SIM for calls if needed, and disable automatic data switching when you want predictable usage.
A QR code and activation code may be single-use. Do not publish screenshots or send them in an open chat.
Check coverage, active line, roaming, APN instructions, remaining data, validity, and device restart before opening a ticket.
Use MX12 calling and support from iPhone or Android.
Mobile access uses the same MX12 account and the telephony workspace selected for that session. Available screens may include contacts, recent calls, keypad, virtual-number and eSIM catalogs, SMS, support, orders, settings, and active-call controls.
Use the official MX12 app, complete email or social login, and review active device sessions in security settings.
Microphone is required for calls. Notifications are required for reliable incoming-call alerts and service updates. Contacts access is optional unless you choose to sync or import contacts.
Before an outbound call or SMS, confirm the selected number or workspace so the customer sees the intended business identity.
Keep push notifications enabled, do not force-close background services unnecessarily, and report the exact missed-call time when troubleshooting.
Use only account-approved recording and transcription settings. The mobile app should reflect server policy rather than create a private local exception.
Revoke the mobile session, disable the device, change the password if necessary, and review recent activity.
Search, save, discuss, sell, or rent marketplace offers.
The MX12 marketplace supports products, services, property, jobs, rentals, and local offers. Visitors can search and save listings; registered users can use listing chat, while seller and company accounts can publish and manage offers.
Find the offer
Search by category and relevant filters, open the full listing, compare the description and seller details, and save useful results.
Confirm in chat
Ask about availability, exact scope, price, location, delivery or rental period, included support, and the next verified step.
Publish responsibly
Choose the correct category and offer type, use accurate images and terms, explain what is included, and keep listing status current.
Business sites, domains, industry chat templates, and custom CRM.
MX12 plans to let a business start from an industry template, configure the site and AI chat, connect a CRM prepared for that business, and publish either under an MX12 path or under a custom domain. Clients will be able to request managed setup instead of assembling hosting, chat, telephony, forms, and CRM separately.
Menu, hours, locations, reservations or enquiries, delivery links, common questions, and lead or booking follow-up.
Services, specialists, price ranges, schedule requests, preparation notes, reviews, and appointment lead capture.
Service information, locations, contact and appointment requests, with strict privacy and no unapproved medical advice from AI.
Practice areas, consultation intake, document checklist, secure handoff, and clear limits against AI giving unapproved professional conclusions.
Listings, locations, availability, enquiry qualification, viewing requests, owner or agent routing, and deal stages.
Service areas, portfolio, quote request, photos, measurements, preferred dates, responsible team, and project follow-up.
Catalog or featured products, delivery and return information, order questions, sales leads, and support escalation.
Programs, schedules, eligibility, consultation or application forms, knowledge materials, and enrollment pipeline.
Choose a template
Select the business type and goal: receive leads, bookings, calls, quote requests, applications, orders, or support conversations.
Configure the business
Add brand assets, contacts, locations, services, prices, hours, languages, legal pages, photos, forms, and the people responsible for replies.
Prepare AI and CRM
Approve knowledge and guardrails, choose the chat intake template, review captured fields, and adapt pipeline stages, roles, tasks, and follow-up rules.
| Publishing option | How it is intended to work | Important client decision |
|---|---|---|
| MX12 hosted path | Publish quickly at an address such as https://www.mirrax12.world/sites/your-business/, with hosting, SSL, updates, and MX12 service connections managed together. |
Choose a unique public slug and confirm what branding or MX12 attribution the selected plan includes. |
| Your existing domain | Connect a domain already owned by the client using the required DNS records. MX12 verifies the domain, enables HTTPS, and publishes after the client approves the final version. | Keep registrar access private, understand which DNS records change, and preserve email records when changing website routing. |
| Buy a domain through MX12 | Search availability, review registration and renewal price, submit accurate registrant details, pay, and let MX12 complete technical connection and renewal management. | Ownership, renewal date, privacy options, registrar lock, transfer eligibility, and any country-domain requirements must be shown before purchase. |
| Transfer the domain to the client | After identity, payment, and registrar eligibility checks, MX12 provides or uses the approved transfer process so the client can move the domain to another registrar. | The client confirms the receiving registrar, authorized contact, transfer code handling, and whether hosting or email should continue after transfer. |
Each template should include starter questions, required intake fields, service-specific FAQs, prohibited claims, qualification steps, and human escalation triggers.
Start with recommended pipelines and fields, then let the company rename stages, add fields, assign roles, connect forms and calls, and decide which automation is allowed.
Website chat, forms, virtual numbers, SMS where supported, and support requests should create or update the correct CRM contact without uncontrolled duplicates.
The recurring plan should state hosting, template license, maintenance, backups, included edits, traffic or usage limits, support level, domain cost, and exit terms.
The agreement should distinguish client content and domain rights from MX12 template code, platform features, licensed assets, and third-party services.
AI may prepare copy and configuration, but publication, paid domain registration, DNS changes, imports, and customer-facing promises require explicit client confirmation.
| Planned lifecycle | Client-visible result |
|---|---|
| 1. Draft | A private preview with selected template, business information, missing-item checklist, and estimated recurring services. |
| 2. Configure | Editable pages, branding, languages, forms, AI behavior, lead fields, CRM pipeline, responsible people, and communication channels. |
| 3. Review | A launch checklist for content, mobile layout, forms, phone routing, chat handoff, privacy, domain, analytics, and billing. |
| 4. Publish | The approved MX12 path or custom domain becomes live with HTTPS and the enabled MX12 services. |
| 5. Operate | Leads, conversations, tasks, calls, and deals flow into the selected workspace with visible ownership and status. |
| 6. Improve | Clients review analytics and conversations, update knowledge, adjust CRM stages, and request design or content changes. |
| 7. Renew or exit | Renew hosting and domain services, export permitted business data, disconnect integrations, or follow the documented domain-transfer process. |
MX12 and its AI should never publish a site, register a paid domain, change production DNS, or import customer data without a clear preview and authorized confirmation.
Before purchase, the client should see recurring costs, domain ownership and transfer terms, export options, cancellation effects, and which parts require MX12 hosting.
Keep payment and balance details easy to verify.
Balance
Shows available funds or credits connected to your account.
Payments
Shows recent top-ups, package purchases, and payment status.
Invoices
Use invoices or receipts when you need accounting confirmation.
Refresh the page. If it still does not appear, create a ticket with amount, date, payment email, and receipt.
Do not create multiple duplicate tickets. Send one request with screenshots and the exact line you want checked.
Protect your client account before you need urgent help.
Go to your account settings and find the authenticator setup area.
Add MX12 to Google Authenticator or another compatible 2FA app.
Enter the current 6-digit code. After that, future logins may ask for this code.
Review signed-in devices, remove access you do not recognize, and revoke a lost or replaced phone.
Give each person only the role needed for their work. Remove former members promptly and review owners and administrators regularly.
Use approved business information only. Keep credentials, private customer data, legal identity documents, and unrestricted internal files out of public AI sources.
Keep registrar credentials private, use 2FA, confirm every DNS change, preserve email records, and document who owns renewal responsibility.
Protect SIP credentials, revoke unused devices, restrict recording access, and investigate unusual calls or spend quickly.
Verify the requesting person and company authority before exporting CRM data, transferring a domain, or changing account ownership.
Use these rules when an AI assistant explains or guides MX12.
| Service area | Status in this guide | AI response rule |
|---|---|---|
| Accounts, companies, tasks, support, CRM, AI settings, widgets, telephony, eSIM, PBX, mobile APIs, marketplace, billing, and security | Available functions exist in the current MX12 project; exact access still depends on role, account, plan, provider, country, and enabled configuration. | Explain the steps and conditions. Never claim a button, service, number, price, or permission is available until the user’s account shows it. |
| Industry website templates, managed site rental, MX12 path publishing, custom-domain publishing, domain purchase and transfer, generated industry CRM | Planned product direction. | Describe the intended workflow, collect requirements, or offer early-access contact. Never describe it as live self-service unless MX12 confirms activation. |
State what will change, which account or workspace is affected, expected cost or renewal, required permissions, and whether the action can be reversed.
Require explicit approval before purchases, publication, DNS changes, domain registration or transfer, data import or export, role changes, number routing, deletion, or customer-facing commitments.
Request only the account, service, timestamp, public URL, and safe diagnostic context needed. Never request passwords, one-time codes, private keys, full card data, or unrestricted identity documents in chat.
If price, availability, regulation, coverage, renewal, or provider status may have changed, direct the user to the live catalog or account and avoid guessing.
Continue in the existing ticket, task, deal, or conversation when it is the same issue. Create a new item only for a separate outcome.
Summarize the goal, affected workspace, relevant service, exact error, timestamp, checks already completed, and the next decision required from a person.
Fast fixes for common client issues.
- I cannot log in
- Check password, email spelling, authenticator code, and whether the email inbox has a verification message.
- Chat is not answering
- Refresh the page, start a new chat, or create a ticket if the issue needs follow-up.
- Ticket has no reply yet
- Open the ticket and check status. If MX12 is waiting for details, add the missing information in the same request.
- Mobile layout looks wrong
- Refresh once, rotate back to portrait mode, and send a screenshot with device model if the issue remains.
- Telephony activation is waiting
- Check whether documents, balance, or country review are still pending. If everything looks complete, send one ticket with the number or package name.
- Website calling cannot connect
- Confirm the number service is active, then send the exact error text and attempt time. MX12 can refresh the route between the number and the calling profile.
- A task is missing or cannot be edited
- Confirm the selected company, your role, task filters, responsible person, date range, and whether the task belongs to another workspace.
- A CRM contact or deal looks duplicated
- Compare email, phone, company, and source before creating another record. Keep the best record and request a reviewed merge instead of deleting history blindly.
- AI gives an outdated or unsafe answer
- Save the conversation, identify the wrong claim, correct or remove the source, tighten the relevant guardrail, and test the same question again.
- An eSIM is installed but has no data
- Check the active data line, coverage, remaining data, validity, roaming and APN instructions. Do not delete the eSIM unless support confirms it can be installed again.
- A custom domain does not open the site
- For future site hosting, check domain verification, DNS records, propagation, HTTPS status, and whether the domain is attached to the intended project. Do not repeatedly change records while propagation is in progress.
Client questions answered quickly.
Should I use chat or a ticket?
Use chat for quick questions. Use a ticket when the request needs tracking, files, billing review, or a later follow-up.
Can I add more information after submitting a ticket?
Yes. Open the same ticket and add the new message, screenshot, link, or receipt.
What information helps support move faster?
Your account email, exact problem, expected result, actual result, screenshots, links, and the time the issue happened.
Where do I get the widget code?
Open your dashboard, go to the widget or chat settings area, copy the public key, and use the code example from this guide.
What should I check before asking about the widget?
Confirm the public key, domain allowlist, script placement, browser console errors, and whether the widget appears in an incognito window.
Why can a number be active but calling still needs setup?
The number purchase and the calling route are separate steps. Activation confirms the number exists on the account; calling setup connects it to the correct MX12 route and webphone profile.
What is the difference between a route and an extension?
The route is the provider-side SIP/PBX login used to receive calls from the number. The extension is the short internal number your webphone or app uses after routing is ready.
Can MX12 create tasks for our company projects?
Company members can use the task board for shared work with descriptions, status, priority, dates, responsible people, files, and task chat. Available actions depend on company membership and role.
Can we customize CRM for our business?
Current My CRM provides contacts, deals, pipeline, tasks, notes, activity, and settings. Deeper ready-made industry pipelines connected to managed business sites are part of the planned product direction.
Can AI use our website and company documents?
Yes, when they are approved as knowledge sources or allowed web sources. Keep information current, set source priority and guardrails, and never upload credentials or unrestricted private customer data.
Can I publish a business website under the MX12 domain?
This is a planned service. The intended options are an MX12-hosted path for quick launch or a connected custom domain after verification and client approval.
Can MX12 buy and later transfer a domain for me?
This is part of the planned domain service. Before payment, MX12 should show ownership, registration and renewal cost, privacy options, transfer eligibility, and exit terms. Transfer must follow identity, authorization, payment, and registrar requirements.
Will one site template work for every industry?
No. Each industry should start with its own pages, lead fields, AI chat questions, prohibited claims, CRM stages, and escalation process, then be adjusted to the real business.
Do I need internal team documentation?
No for normal client use. This page includes a safe AI-readable reference, while private credentials, provider internals, security procedures, and employee-only operating details must remain in protected internal documentation.
When in doubt, send one clear request.
Support request
Best for account, payment, technical, and service questions that need tracking.
Website chat
Best for quick questions and simple guidance while you are browsing the site.