# Set up your business and connect its domain

Use the owner conversation to configure the offer, profile, client routing and native domain delivery, then inspect the actual result.

Canonical: https://docs.bankeiz.com/business-setup/
Reviewed: 2026-10-28; coordinated packages 129.0.0; ruleset 127.0.0.

## Begin with the work you want done

Business setup happens in your existing Your agent conversation. State the change you want: your offer and client answers, profile details, booking/payment routing, supported team handoff, a work output or your domain. Supply the relevant business context rather than rebuilding another identity. Business access and actual configured service capabilities still apply. Settings offers direct editing of the supported Twin fields; the conversation composes its existing native actions.

## Configure the existing business

1. **Explain the desired change** — For example: set my offer to a 30-minute consultation, explain who it helps, and prepare my existing booking and payment routes. Name actual team destinations when requesting supported handoff.
2. **Attach the exact work when needed** — Use Attach work or an image for the image or Original you intend to use. Do not imply an attachment exists when it has not been selected.
3. **Review the proposed action** — An action card may expose Action details and Run this action. Inspect the actual tool and arguments before choosing it. Read-only inspection and a proposed change remain distinct.
4. **Inspect the result** — Setup updated, Profile saved, Image saved or the actual native result names the completed action. View native result exposes the returned detail. Check the profile, Settings, Contacts or Calendar that the result changed.

## Connect the intended domain

1. **Name the exact domain** — Ask the agent to connect the hostname you own, then inspect the hostname shown in its returned domain result. Saving a hostname alone does not make it live.
2. **Connect the existing provider** — If required, use Connect your provider and approve its actual provider access. Return to this conversation to continue the same connection. Provider credentials stay in the supported connection flow.
3. **Use automatic or manual instructions** — When automatic setup is supported, the result reports actual applied DNS. Otherwise open Domain instructions and copy the shown record type, name and value into your domain provider. Use the exact returned values.
4. **Inspect delivery** — DNS saved means records were applied. Profile verified and Domain is live establish the accepted delivery state. Open your domain appears for the actual verified live URL.

## Inspect domain progress and result

**The connection result retains its scope**

| Display | Meaning | Next step |
| --- | --- | --- |
| Connect your provider | Provider approval is required. | Complete that connection, then continue the same setup. |
| DNS saved | The provider accepted the shown records. | Keep chatting while delivery is checked; inspect the separate profile result. |
| Waiting for delivery | Live delivery is not confirmed yet. | Ask to check the same domain later. |
| Profile verified / Domain is live | The checked domain and profile route match. | Open your domain and inspect it. |
| Domain changed / Checks stopped | The saved target changed while another check was running. | Review the current hostname before another request. |

## Create, seal and publish the intended work

For supported creation, state the output and useful brand/audience/offer context. Inspect the actual creation workspace/run result; accepting a request does not establish a rendered asset. To seal attached work, choose the actual file(s) and ask to seal their exact bytes. The conversation’s Original sealed result retains the proof privately; ask explicitly to publish that selected sealed Original when public delivery is intended. Publishing is a separate native action in this conversation path. Inspect Published or Publication needs checking, then open the actual source/profile. The asset composer’s Create asset route has its own automatic public-sealing sequence.

## Check an interrupted action

A result marked unknown or Result not confirmed is retained and has not been repeated. Ask to inspect current setup, creation, work or domain before another write. Check result on a pending Receiz action continues the same admitted attempt. Public DNS propagation, file selection, profile delivery, generated work and financial execution each have their own result. A successful setup reply cannot stand in for a payment receipt, ownership transfer or new spending permission.

- [Configure the Twin controls](https://docs.bankeiz.com/twin-workspace/)
- [Preserve the publication result](https://docs.bankeiz.com/publication/)

## Implementation sources

- [Owner chat actions, attached files and native result retention](https://github.com/kojibai/reality-grade-banking/blob/v4.0.0/src/receiz/business-chat.ts)
- [Existing agent configuration and creation operations](https://github.com/kojibai/reality-grade-banking/blob/v4.0.0/src/receiz/business-setup.ts)
- [Setup approval, DNS details and delivery evidence](https://github.com/kojibai/reality-grade-banking/blob/v4.0.0/src/features/messages/BusinessReceipts.tsx)
- [Domain instructions, provider connection and exact checks](https://github.com/kojibai/reality-grade-banking/blob/v4.0.0/src/receiz/business-dns-tools.ts)

## Related documentation

- [Your agent, identity and connected context](https://docs.bankeiz.com/agents/)
- [Configure your Twin and inspect its work](https://docs.bankeiz.com/twin-workspace/)
- [Activate Business, add credits and resume work](https://docs.bankeiz.com/credits/)
- [Publish, share and preserve an Original](https://docs.bankeiz.com/publication/)