Find the answer. Keep building.

Start with what the business does and where it operates. You can refine the company name, services, service area and operating details after the workspace is created.

No. Use the existing-business path when it is offered. Neuron can use information you confirm from your current website or public business listing, then you review the result before relying on it.

It is the shared operating record behind the product: customers, requests, bookings or jobs, website data and connected communication context. Extra modules build around that record instead of creating separate copies of the same customer.

Choose the market where the business will actually operate. Phone numbers, payments and local requirements vary by country, so use Countries & availability to check the current market status before planning a launch.

Use the company profile and the relevant workspace for the asset you are changing. Neuron chat and the classic interface are intended to work on the same company state, so you should not have to maintain two versions of the business.

Open the phone-number setup and choose the location you want to serve. Available numbers depend on the provider inventory in that market, so a specific area code cannot be assumed until it is shown as available.

Often that means porting or forwarding, and the exact path depends on the current carrier and country. Confirm the migration path before cancelling the old line so customers do not lose the number during the move.

Business messaging can require carrier registration and verification. The phone workspace should show the messaging state for the number; a voice-ready number is not automatically proof that outbound business SMS is approved.

Call routing depends on the phone and receptionist configuration. Use the routing controls for the business rather than creating a second disconnected phone workflow.

When enabled for the business, it can answer calls, collect the customer request and relevant job details, and move the caller toward the configured next step such as booking or human follow-up.

Use the call-routing rules available for the business. Transfers and fallback behavior depend on the active phone setup, so configure them where the number and receptionist are managed together.

Use only the voice languages shown as available for the account or market. Website and chat language support is a separate capability and should not be treated as proof that the voice line supports the same language.

Where call recording or transcription is enabled, the resulting call context belongs with the customer and request rather than in a separate notebook. Recording and consent rules vary by jurisdiction, so use the configured product behavior for the market.

The CRM is the business record for customers and the work around them: requests or leads, bookings, jobs and the communication context the enabled workflows create.

Migration options depend on the source and the tools currently enabled for your account. For a bulk customer or job migration, confirm the supported import path with support instead of assuming a spreadsheet format will be accepted.

Use one customer record whenever possible so calls, jobs and payments do not split across identities. If duplicates cannot be safely corrected with the controls in your workspace, ask support before deleting records.

Team access is role-based where that feature is enabled. Use the account's current team and permission controls; available seats and advanced team capabilities depend on the current plan rather than a number copied into this help page.

Yes. The product includes a website workflow for publishing the business and its services. What is included by default and what requires a higher plan is shown in the current product and pricing screens.

A custom domain can be connected when that capability is enabled for the account. The domain must point to the values Neuron gives you, so expect a DNS change at the registrar or DNS provider.

No. A website domain and an email mailbox are separate services. Do not assume a mailbox exists just because the domain resolves to the website.

Use the website workspace or the Neuron workflow that edits the same site state. Check the published result after major changes, especially service areas, contact details and pages intended for search.

Customer card payments use the business payment connection. Where Stripe Connect is supported, complete that connection and provider verification before expecting customer-facing card payment to be available.

The payment account may not be connected or fully active for that business. Neuron is designed to hide or disable card payment when the connected account is not ready instead of sending the customer into a broken checkout.

Payment activity belongs with the business record it relates to, such as the customer, invoice, estimate or job. Use that history rather than keeping a second manual payment log.

Use the payment workflow available for the transaction. Provider rules and the transaction state can affect what can be refunded, so do not promise a refund path to a customer until the payment record shows the available action.

Use the Pricing page and the billing controls in your account. Those are the source of truth; this Help Center intentionally does not repeat dollar amounts that could change.

The account should show the next billing or entitlement state for the feature being tried. Check that state before the trial ends rather than relying on an old screenshot or message.

Use the billing or usage view provided for the active product. Metered limits can differ by feature and plan, so the live account value is the number to trust.

Use the current billing controls when they are available. If the needed control is not shown, contact support before the next renewal and identify the company and plan you want changed.

Use the same sign-in method the account was created with. If Google sign-in was used, try that route rather than creating a second email account for the same business.

Use the profile controls if the change is available there. If the login identity itself must change and no control is shown, contact support from an address you can still access so ownership can be verified safely.

Where language preferences are available, update the account locale or language control. Product language and voice-language availability are separate settings.

Use the Privacy Policy and contact route for access, export or deletion requests. Include enough information to identify the account, but do not send passwords or full payment-card data.