# Concierge public documentation

Concierge brings native Codex Voice orchestration onto the phone network.

## Concierge docs
Start with setup, learn what Concierge can do with the phone, or review its safety and privacy boundaries.
URL: /docs

### Start here
- Set up Concierge: connect Codex, activate a plan, verify your phone, and check readiness.
- Use Concierge: learn how native Codex Voice orchestration reaches the phone network.
- Work Awareness: understand the optional short work snapshot and its readiness requirements.
- Security and privacy: learn who Concierge trusts and what each caller can access.

### New to Concierge?
1. Sign in to Concierge and confirm the current durable account state.
2. Connect the paired computer that runs the current Codex phone target when setup asks.
3. Activate the requested Concierge plan through the website when setup reaches activation.
4. Verify possession of your owner phone when setup requests verification.
5. Get or reuse your Concierge number when setup reaches phone provisioning.
6. Check readiness before you expect live phone service.

## About the beta
Concierge gives your Codex agent a phone number. Call to talk through a task, leave the work with your agent, and let it call you when it needs your input. Your work stays in Codex.
URL: /docs/beta

### Take the conversation with you
Use Concierge when you want to work with your agent without sitting at the keyboard. You can discuss a proposal on a walk, ask about a task while making lunch, or make a decision that lets your agent keep going.
Leave a review with your agent: Before you step away, ask your agent to review a proposal. On the phone, talk through the tradeoffs and choose what to change. After you hang up, your agent can continue the work on your connected computer.

### Calls that move the work forward
- Call your Concierge number to talk with your Codex agent about the work.
- Ask your agent to call you when your input would help. Tell it what deserves a call and what can wait.
- Keep the task in Codex, with its conversation, decisions, and results available when you return to the screen.
A call ending does not finish the task. Your agent can continue on the connected computer, ask for a decision when it needs one, or leave the result for you to review.

### Pick up where you left off
Enable Work Awareness if you want recent work updates to help orient your calls. Your agent shares short updates from work on the connected computer, so you can start with what has changed instead of explaining everything again. When a decision needs detail, your agent can check the task itself.
Recent-call context, called Hot Context, helps reconnect a recent conversation or missed callback with its Codex task. You can review or dismiss that context. Both features use limited, recent context: updates expire, and a later call may need you to name the task again.
Work Awareness is optional. It is not a live view of every task on every computer, and an unavailable computer cannot supply current work updates. Your private work context is not shared with external callers.

### Choose when a call is useful
Ask for decisions, not every update: Tell your agent: 'Keep reviewing the proposal. Call if you need me to choose between options; leave routine updates in the task.' Your agent can then weigh whether your answer would unblock the work before attempting a callback.
Set quiet hours and calling preferences to shape when Concierge may reach you. Permission to work is not blanket permission to call. Your agent still needs an allowed reason to contact you, and your calling controls apply.
Calendar context depends on the tools and information available to your agent. Setting quiet hours does not connect your calendar or give Concierge access to your schedule.

### What you need
- Eligible Codex access and a supported computer connected to Concierge. Check the setup guide for the available installer and requirements.
- An active Concierge subscription, a verified owner phone, and a Concierge number.
- An awake, connected computer for phone calls and work that continues after you hang up.
Follow the setup guide to connect your account and computer, then check phone readiness before your first call.

### Beta limits to know
- Codex is the supported phone target. Concierge does not currently connect phone calls to Work.
- The beta is voice-only. Normal SMS, MMS, and carrier voice-note messaging are not included.
- Your Concierge number handles one live phone conversation at a time.
- Unknown callers are not admitted by default. You control who may reach your agent; caller access does not grant access to your private work.
- Calls use your plan's phone allowance. Check your account for available minutes and the next allowance window.

### Looking ahead
We want to bring Concierge to more of the places you already work with agents. Work phone support is a future direction, dependent on a supported way to connect its conversations and live voice to a phone call.
We will share additions in Updates as they become available. Choose the beta for the capabilities described here; future features have no promised release date.

## What is Concierge?
Concierge brings native Codex Voice orchestration onto the phone network. Codex remains the reasoning and work-context authority.
URL: /docs/what-is-concierge

### What makes Concierge different
Concierge does not create a second voice agent. It carries the native Codex Voice orchestration path into a telephone conversation.
The top-level Codex orchestrator can keep talking while it delegates work, receives results, and steers more work in the same native context.

### Current phone target
Codex is the current beta operational phone target.
Work remains a full first-party cloud orchestrator with durable context, cloud continuation, cross-device history, and native Work Voice.
The supported Work surface does not currently expose the addressable conversation and external Voice/media-control boundary Concierge needs to attach a phone call.

### What Concierge is not
- It is not a generic AI receptionist.
- It is not a shadow GPT or separate reasoning runtime.
- It is not a duplicate task system.
- It is not a competing transcript or personal-memory database.

## Set up Concierge
Setup is resumable. Follow the next action returned by Concierge instead of restarting completed steps.
URL: /docs/setup

Availability: The complete phone setup journey is still being validated end to end.

### Before you start
- Use the Concierge account you want to own the phone identity.
- Have the owner phone available for possession verification.
- Have the Codex computer that will act as the current phone target.

### Set up Concierge
1. Sign in to the Concierge account you want to use and read its current durable setup status.
2. Select Codex as the current beta phone target without starting a phone purchase.
3. If Concierge is not installed in Codex, use the owner-approved GitHub package source shown by the website handoff, review its hooks, and then return to Codex. A missing source means public distribution is not ready; do not use an untrusted checkout.
4. Connect the computer that will provide the current Codex phone runtime, then check readiness.
5. If the status says the account has no active Concierge entitlement, choose the requested plan through website Checkout; the plugin only explains the status and does not start a subscription.
6. Wait for durable activation confirmation before leaving Checkout. If the return is still pending, check again rather than paying again.
7. Complete owner phone verification when the entitled setup status requires it.
8. Use the retained Concierge number after the account, target, readiness, and verification prerequisites are ready. If no retained number exists, complete phone setup through the Concierge website before using the plugin.
9. Check readiness again and follow the next returned action.

### Verification SMS is setup-only
Important: Concierge does not support normal SMS or MMS in the beta. Verification SMS only proves owner phone possession during setup.

### Resume an interrupted setup
Concierge stores durable setup state. An accepted or consumed verification step can resume without repeating completed provider work.
If a provider result is uncertain, Concierge keeps the operation uncertain and reconciles before another consequential attempt.

## Connect more than one computer
Concierge can keep more than one Codex computer connected to the same account, while each call still runs on one computer.
URL: /docs/computers

Availability: Computer management is included in the replacement beta. Live phone work requires an installed, trusted and paired Codex integration; a connection listing alone does not prove task access. Public native installation and complete phone-work acceptance remain pending.

### Connect another computer
1. Open the Concierge computer management page: https://dialconcierge.com/account/computers.
2. On the computer you want to connect, open Codex with the Concierge plugin active.
3. Say ‘Connect this computer’ and use the same Concierge account.
4. Return to computer management to review connection and readiness state.

### One call uses one computer
Connecting several computers does not make one call run on all of them. A call runs on one selected computer in a native Codex conversation.
Connected-computer preferences and readiness are separate from the exact host selected for an active call. Concierge does not automatically merge all projects, threads, files, or history across computers.

### What shared project context means
Connecting computers does not automatically give every call access to their projects and conversations. With optional Work Awareness enabled, Concierge can remember a short-lived topic checkpoint and its source computer. These checkpoints cover only some work; they are not a list of every project.
If a known topic belongs to an unavailable computer, Concierge can name the computer and the time of the checkpoint. It may ask you to open Codex and its Concierge connection there. Unavailable does not necessarily mean powered off. After reconnecting, Concierge must still check whether its native tools can read the requested work.
The first implementation adds bounded task tools to newly created owner phone conversations on the connected computer. Older resumed conversations may lack those tools. A successful read can establish access to a selected task; registration or a saved checkpoint alone cannot. These tools do not combine native histories across computers.
If Concierge cannot identify the associated computer, it should say that it does not know rather than inventing a device link.

### Read pushed work from GitHub
An optional work checkpoint can include a known GitHub repository and branch. If its computer is unavailable, Concierge can use GitHub tools available to the conversation to check the latest pushed work. Private repositories need your existing authenticated GitHub access.
A repository link is not proof that Concierge can read it. A cloud answer should identify the repository and branch or commit it checked. GitHub cannot recover uncommitted or unpushed changes, local-only files, or your native Codex conversation history. If no repository is known or access is unavailable, Concierge should say so.

### Manage connected computers
Use the connected-computer dashboard to inspect and manage the computers associated with your Concierge account: https://dialconcierge.com/account/computers.
- Review each computer's name, connection status, and last-seen time.
- Choose a preferred computer for new calls. Preference changes wait until active or uncertain calls are resolved.
- Rename a computer when its label is unclear.
- Disconnect a computer when it is no longer needed; Concierge refuses a disconnect that would interfere with an active or uncertain target call.

## Check phone readiness
Use Concierge readiness state as the source of truth. Do not infer readiness from having a phone number alone.
URL: /docs/readiness

### What live phone service needs
- An active Concierge account and entitlement.
- A verified owner phone state when required.
- Codex selected as the current phone target.
- A reachable paired computer with the required Codex capability.
- A ready Concierge phone identity and provider route.
- Available occupancy and phone allowance for an allowance-consuming call.

### If the paired computer is offline
Live phone Voice is unavailable while the required paired Codex computer is offline. Concierge does not replace it with another voice brain. The responsibility remains with native Codex and can continue or recheck when the required native runtime is available.

### Windows availability
Current beta status: Windows is not yet fully validated for production use. Installation, pairing, recovery, runtime, and uninstall still need final validation.

## Using Concierge
Use Concierge when native Codex work needs a telephone conversation, a human dependency, or a well-timed owner decision.
URL: /docs/using-concierge

Availability: Work Awareness is included in the replacement beta and requires explicit owner opt-in, a ready Codex integration and current validated work updates. Public native installation and the complete phone-work demonstration remain pending. The example below is illustrative, not a recorded result.

### Talk to the orchestrator running the work
A live Concierge call uses native Codex Voice orchestration. The same top-level orchestrator can talk, delegate, receive results, and steer more work.
Example: Review these files while we talk. Delegate the security review, then tell me what needs my decision.

### Which model powers Concierge phone calls?
Concierge uses GPT-5.6 Luna with medium reasoning by default.
To change it, ask Concierge in ChatGPT or Codex: “Use Astra with high reasoning for new phone conversations.” You can also ask to switch back to Luna with medium reasoning.
Changes apply to new conversations. Calls that resume an existing conversation keep its model. Your connected Codex computer must support the model you choose; saving a preference does not guarantee it can run. This setting changes the reasoning model, not the speaking voice.

### Delegate a real-world call
Concierge can plan permitted personal, transactional, and individually directed calls to a restaurant, business, support line, or person.
Example: Call the restaurant about a table for four. Handle the ordinary details within the constraints I gave you.
Availability: Outbound carrier calling is still being validated for the current beta.

### Return only when your attention is worth it
Concierge values the expected benefit of an interruption instead of treating every urgent event as a reason to call.
Current decisions can consider blocking state, deadlines, expected answer time, quiet hours, preferences, Calendar context, current activity, occupancy, and phone allowance.
Example: Keep working. If a five-second answer would unblock the review, check whether I am in a meeting before deciding whether to interrupt me.
Calendar is context, not a blanket rule: A meeting, focus state, sleep, driving, or quiet hours can increase interruption cost. These signals do not automatically prove that contact is forbidden.

### Keep native work alive after hangup
Hangup ends Voice. Hangup does not automatically end the native Codex responsibility that existed before the call ended.
The same native work can continue, block, complete, or schedule a later recheck where the current Codex surface supports it.

### Resume the right current context
Current context selects bounded continuity into native Codex history for the next verified owner call.
You can dismiss the selected current context. The selected current context is not itself an editable transcript or memory record.
Owner-authored context notes are a separate bounded editable surface. Notes provide context but do not create authority or confirmation.

### Start with a short work snapshot
Work Awareness is an optional owner-controlled briefing for the next verified owner call. When enabled, trusted native Codex roots can keep one short, expiring update about meaningful work; native Codex remains the source of truth.
1. Ask Concierge to enable Work Awareness for your account, then continue working in Codex.
2. At a meaningful checkpoint, a trusted root can publish a concise progress, decision, or next-step update.
3. On a call, ask, ‘What needs my attention?’ Concierge can start with up to four current validated updates.
4. Choose one update to explore. If deeper native retrieval is needed, Concierge can acknowledge it and keep the conversation moving when the current Voice path supports that concurrency.
5. Tell Concierge when an update is no longer useful, or ask to turn Work Awareness off. Reading an update alone does not clear it.
Example first call (illustrative): You: ‘What needs my attention?’ Concierge: ‘The launch date needs your decision, and the docs are ready for review. Which should we take first?’ You: ‘The date. What are the tradeoffs?’ Concierge, once the native lookup has started: ‘I’m checking the launch thread. The latest update asks whether Friday still works for you. Has that changed?’ When the result arrives, Concierge explains the current tradeoffs and follows your decision.
Work Awareness does not replace owner returns. If native work truly needs a decision, the existing owner-attention and return policy still decides whether a phone interruption is warranted.

### Move a task forward, then leave your desk
Start with work already attached to the conversation. A fresh phone conversation does not guarantee access to every existing Codex task; Concierge should explain when it cannot open or redirect another task from that call.
1. Say what you need from the call: ‘I have two minutes. What decision does this launch task need?’
2. Ask for the current facts before deciding. A short work update provides orientation; the native task owns the full context.
3. Give a concrete direction and stopping point: ‘Use a three-minute live demo. Prepare the draft, and leave publication for my review.’
4. Listen for what actually happened. ‘The instruction reached the task’ is different from ‘the draft is complete.’ If the connection drops during a send, Concierge should check its status before sending again.
5. State any return preference that needs changing. ‘Don't call when the draft is done’ leaves an existing blocker-call preference intact.
6. When returning to the same native conversation, ask what changed after you left. A saved conversation alone does not mean work finished while you were away.
If your instruction is ambiguous: You: ‘Include it.’ Concierge: ‘Pricing, the setup walkthrough, or both?’ A clear reference needs no extra confirmation; two materially different interpretations need one short clarification.

### Use contacts without turning them into authority
Concierge can keep bounded contact metadata, explicit contact authority, admission state, and learned communication preferences.
Contact memory does not automatically admit an inbound caller. Admission does not create owner authority.

### One live user-facing conversation at a time
The current phone identity supports one live user-facing phone conversation at a time. Concierge does not silently hang up a current call to start another.

### Treat uncertain provider outcomes as uncertain
Concierge does not assume that a timed-out or ambiguous provider result failed. It reconciles authoritative provider state before another consequential attempt.

### Do not assume carrier controls are product controls
A carrier can support a control that Concierge does not expose to the agent. Concierge must not claim keypad, hold, transfer, conference, screening, or voicemail control unless the current product exposes it.

## Make and manage calls
Concierge is Voice-first. Use the phone when the conversation or interruption adds enough value to justify it.
URL: /docs/calls

### Phone directions
- Make a permitted external call for a personal or transactional task.
- Receive an admitted inbound call through the current Codex phone path.
- Return to the owner when a short decision materially unblocks native work.
- Continue native work after hangup when the work obligation remains open.

### No normal messaging fallback
Voice-first beta: Normal SMS, MMS, and carrier voice-note messaging are not beta communication surfaces. An unavailable call remains native work, defer, or recheck.

## Ask Concierge to make a call
State the goal, destination, and important limits. Concierge still applies current authority, policy, purpose, allowance, occupancy, and provider checks.
URL: /docs/calls/make

Availability: Authorized outbound carrier calling is still being validated for the current beta.

### Delegate the call
1. State who Concierge should call.
2. State the personal or transactional purpose.
3. Give the limits that matter for the conversation.
4. Tell Concierge which decisions require you.
5. Let Concierge return an actual call result or an explicit blocker.
Example: Call the hotel and ask whether late check-in is possible. Do not change the reservation without asking me.

### Purpose can only narrow authority
An allowed purpose lets evaluation continue. It does not create contact permission, owner authority, phone capacity, provider readiness, or effect authority.

## Receive a call
A call to your Concierge number does not automatically receive owner access or private owner context.
URL: /docs/calls/receive

Availability: Inbound calling is still under end-to-end beta validation.

### If Concierge thinks the caller may be you
Caller ID is only a candidate signal. Owner-only Voice and private context require durable owner enrollment plus exact call-time authentication after trusted carrier ingress.

### If the caller is external
External speech is task input. It does not create owner authority, unrelated Codex access, or permission to change owner policy.
Third-party inbound is private by default. Contact memory and inbound admission remain separate decisions.

## Let Concierge return when work needs you
Ask Concierge to return only when the expected value of interrupting you is material.
URL: /docs/calls/owner-return

Availability: Owner-return calling is still being validated on the live carrier path.

### How Concierge values an interruption
- How much work is blocked.
- How short the expected owner answer is.
- Whether a real deadline is at risk.
- Whether useful work can continue without the owner.
- Current quiet hours, preferences, Calendar, and activity context.
- Current occupancy, capability, and phone allowance.

### Calendar-aware timing
A current meeting or focus state increases interruption cost. Concierge should not pretend that a stale or unknown Calendar state is current.

## What happens after you hang up
Hangup ends Voice. It does not automatically cancel unfinished native Codex work.
URL: /docs/calls/after-hangup

### Native work can continue
The same top-level native work owner can continue, block, complete, or satisfy a permitted return obligation after the call ends.

### Scheduled rechecks
Where supported, the same Codex work can schedule a later recheck and read the current state again when the recheck runs.
Fresh authority is required: A scheduled recheck does not authorize a call and does not reserve phone allowance. Any later phone action must pass current checks again.

## Current context and owner notes
Current context selects bounded native Codex continuity for a verified owner call. Owner notes are a separate editable context surface.
URL: /docs/current-context

### Current context is derived
Concierge derives a current continuity selection from native Codex work. The selection is not a copied transcript or a general memory database.

### Dismiss the selected current context
The owner can dismiss the selected current context so Concierge does not automatically use that selection for the next verified owner call.
Do not confuse dismissal with editing: The current-context selection is dismissible. The selected continuity pointer is not directly editable.

### Owner notes are separate
Owner-authored notes are bounded editable context. They can help the native conversation, but note text cannot create policy, confirmation, communication authority, or consequential authority.

## Safety boundaries
Model intent never replaces identity, authority, policy, capability, commercial, provider, or final effect checks.
URL: /docs/safety

### Authority stays outside model text
A prompt, skill instruction, purpose label, phone number, or caller statement cannot mint trusted current-root or consequential-effect authority.

### Purpose narrows
Purpose admission can stop a call. An allowed purpose cannot bypass the other checks required for a real-world effect.

### Emergency calling
Unsupported: Concierge does not support emergency calling. Do not use Concierge to contact 911 or another emergency service.

## External callers
External caller speech is task input, not owner authorization.
URL: /docs/safety/external-callers

### External access stays task-scoped
- An external caller does not receive owner authority.
- An external caller does not receive unrelated Codex context.
- An external caller does not receive owner-only current context or private notes.
- An external caller cannot enlarge the native root's authority by saying that an action is approved.

### Contact memory is not admission
Concierge keeps contact memory separate from inbound admission. Both remain separate from owner authentication.

## Data and privacy
Codex owns the authoritative native conversation context. Concierge keeps bounded operational data needed to coordinate the phone service.
URL: /docs/data-and-privacy

### Native conversation context
Concierge does not create a competing semantic transcript, task, or personal-memory database for native Codex work.

### Operational data
Concierge can keep account, phone identity, routing, contact, policy, allowance, usage, readiness, and bounded continuity coordination data.

### Work Awareness
When explicitly enabled by the owner, Work Awareness stores up to 24 short current native-work updates. Updates expire after four hours by default, with a maximum lifetime of 24 hours and scheduled content cleanup. Turning it off clears stored updates; it does not erase content already delivered into native Codex history.

### Call recording
Call recording is not enabled by default in the current product. Do not interpret this as a promise that calls can never be recorded.

### Retention and international processing
Concierge keeps account and identity records, billing references, phone-resource records, call metadata, owner-managed contacts, bounded workflow results, authorization records, routing references, and provider reconciliation records as needed to provide and secure the service.
Retention also supports authorized continuity, reconciliation, legal obligations, dispute resolution, and fraud prevention. The current implementation does not impose one fixed deletion period across all durable record types.
Support requests remain while open. After a request is closed, the current beta implementation schedules deletion after 180 days. Security and diagnostic logs use bounded retention configured for the relevant system or provider rather than one repository-wide deadline. The initial beta is offered in the United States, and service providers may process information elsewhere as needed to provide and secure the service.

## Current availability and limits
Carrier features are not automatically Concierge features. Some current beta phone paths are still being validated end to end.
URL: /docs/availability

### Current product shape
- Codex is the current beta phone target.
- Telnyx is the canonical production carrier.
- Normal SMS and MMS are not beta communication surfaces.
- Carrier voice-note messaging is not a beta communication surface.
- Scheduled rechecks can resume supported same-thread Codex work without granting phone authority.

### Still being validated
- Complete end-to-end Codex phone path.
- Owner-return calling on the live carrier path.
- Complete phone setup journey.
- Inbound calling end to end.
- Authorized outbound carrier calling.
- Windows production installation and runtime.

## Phone allowance
Your Concierge account has a bounded owner-visible phone allowance in a recurring seven-day window anchored to real service activation.
URL: /docs/phone-allowance

### How the allowance window works
- Concierge includes 7,200 seconds, or 120 minutes; Concierge Pro includes 60,000 seconds, or 1,000 minutes.
- The recurring seven-day window starts from real service activation.
- Monthly billing and the seven-day phone window are separate.
- Unused time does not roll over.
- Concierge does not add automatic paid overage at launch.
- Your selected entitlement sets the owner-visible phone time available in the recurring seven-day window.
- The recurring seven-day window starts from real service activation.
- Unused time does not roll over.
- Concierge does not add automatic paid overage at launch.

### Finish an admitted active call
A qualifying call that was admitted below the allowance cap can receive up to 900 additional seconds to finish the current call.
The finish period is non-reusable. It does not replenish allowance for another call.

## Your Concierge number
Concierge keeps one phone identity for the selected phone target. A target change does not require a second number by default.
URL: /docs/phone-number

### Reuse the existing number
If Concierge already owns a valid retained number for the account, setup should preserve it instead of creating a second number only to repair a target connection.

### Number ownership and service are separate
Phone-resource ownership and communication entitlement are separate facts. A provider response can also require reconciliation before Concierge treats a number as released.

## Billing
Concierge costs $15 per month and uses a separate recurring seven-day phone allowance.
URL: /docs/billing

### Plan and phone allowance
- $15 per month.
- 7,200 phone seconds per recurring seven-day activation-anchored window.
- No rollover.
- No automatic paid overage at launch.
- A qualifying admitted active call can use the non-reusable finish-current-call period.
Billing and phone windows: Monthly billing and the seven-day phone allowance run on separate schedules.

## Troubleshooting
Start from the current Concierge state. Do not create a second number or repeat an uncertain provider effect as a generic repair step.
URL: /docs/troubleshooting

### The paired computer is offline
1. Open Codex on the paired computer.
2. Open Concierge setup.
3. Check the computer connection state.
4. Select Connect this computer if Concierge shows the computer as disconnected.
5. Check readiness again and follow the returned next action.

### A call or provider result is uncertain
Do not assume the effect failed. Concierge keeps stable operation identity and reconciles authoritative provider state before a duplicate effect is considered.

### Voice is unavailable
Do not look for a hidden SMS, MMS, or carrier voice-note fallback. Leave the responsibility with native Codex, and continue or recheck when the required native runtime is available.

## Frequently asked questions
These answers use the same canonical FAQ source as docs search and contextual Common questions sections.
URL: /docs/faq

## Glossary
The glossary defines user-facing terms. It intentionally omits most internal implementation vocabulary.
URL: /docs/glossary

## Privacy & security
How Concierge protects your access and data
You decide who can reach your agent and when it may call. Concierge checks those permissions before placing or connecting a call.
URL: /trust

### Your account controls access
Codex handles the work. Concierge checks your account and authenticates each owner call before sharing private context.
Knowing your phone number or claiming to be you is not enough to access your private context.

### External callers stay isolated
Someone you allow through can provide information for the current task.
That caller cannot access your unrelated Codex work or private notes, and cannot act with your permissions.

### Caller ID is not enough
Concierge checks owner phone enrollment and authenticates the call using verified carrier information. A matching caller ID alone does not unlock private context.

### A request cannot grant permission
An allowed personal or transactional request still has to pass the other checks. Asking for a call cannot override identity checks, contact permissions, or your phone allowance.

### What Concierge checks before calling
- Your account and subscription
- Permission to contact the person
- Your calling preferences and quiet hours
- The Codex task and connected computer
- Whether a call is already active and phone time is available
- The destination and phone service
- Whether this request has already been carried out

### Avoiding duplicate calls
If the carrier takes too long to respond, Concierge checks what happened before trying the action again.

### Where your data lives
Your conversations and work history stay in Codex.
Concierge keeps the account, phone, contact, permission, and usage information needed to run the service. It also keeps limited coordination data for connecting calls and resuming recent work. It does not create a separate transcript or personal-memory database.

### Permissions are checked again later
Codex can use its supported scheduling tools to revisit a task later.
A scheduled task does not reserve phone time or permission to call. Concierge checks the current permissions and limits when the task requests a call.

### Phone limits still apply
When phone time runs out, an agent cannot bypass the limit by switching to another carrier channel.

### Supported calling options
Telnyx carries production calls. Twilio remains fallback and reference.
A feature offered by the carrier is not necessarily available in Concierge. The availability guide lists the current limits.

### Current beta availability
Some phone and Windows paths are still being validated for the current beta. See Current availability and limits for the latest supported boundaries.

### Limits of these controls
These controls reduce risk. They do not make software or telecom systems immune from compromise.

### Who can authorize an owner action
Owner requests still pass permission checks. External callers can contribute to a task without gaining owner access.

### Phone event flow
Concierge authenticates the call before connecting it to Codex. It checks permissions before asking the carrier to act, and checks the result when the outcome is uncertain.

### Scheduled recheck
When a scheduled task resumes, it checks the current work, permissions, and limits before requesting a call.

## Frequently asked questions
URL: /docs/faq

### What is Concierge?
Concierge brings native Codex Voice orchestration onto the phone network. Codex remains the native reasoning and work-context authority.

### Does Concierge replace Codex?
No. Concierge is the communications layer around native Codex work. It does not create a second reasoning runtime or shadow voice agent.

### Which model powers Concierge phone calls?
Concierge uses GPT-5.6 Luna with medium reasoning by default. Ask Concierge in ChatGPT or Codex, “Use Astra with high reasoning for new phone conversations,” or ask to switch back to Luna with medium reasoning. Changes apply to new conversations; calls that resume an existing conversation keep its model. Your connected Codex computer must support the choice, and this changes reasoning—not the speaking voice.

### Why is Work not a current phone target?
Work has native Voice, cloud orchestration, durable context, and cross-device history. Its supported first-party surface does not currently expose the addressable conversation and external Voice/media-control boundary Concierge needs to attach a phone call.

### Can I connect more than one computer?
The Computers page and context diagnostic are in development. Yes, multiple Codex computers can be connected to the same Concierge account. Each call still uses one exact native host, and computer connections do not automatically merge all projects, files, threads, or history.

### Does Concierge automatically know every project on my computers?
The Computers page and context diagnostic are in development. Connecting computers does not automatically share all their projects or conversations with every call. Optional Work Awareness checkpoints can identify some last-known work topics and their source computers. They expire and do not cover every project. A connected computer still needs an available native tool before Concierge can read its work.

### Can anyone who knows my number control Concierge?
No. Caller ID does not prove owner identity. Owner-only access requires stronger verified owner state and exact call-time authentication.

### How does Concierge know a caller is me?
Caller ID is only a candidate signal. Owner-only phone context requires durable owner enrollment plus exact per-call authentication derived after trusted carrier ingress.

### What can an external caller access?
An admitted external caller remains task-scoped. External speech does not grant owner authority, unrelated Codex context, owner current context, or private owner notes.

### Why does setup use SMS if texting is unsupported?
Setup can use Telnyx Verify SMS only to prove owner phone possession. Normal Concierge SMS and MMS remain outside the beta.

### Can I resume setup after an interruption?
Yes. Concierge uses durable setup state. Completed verification states can resume without repeating provider work that already completed.

### Can Concierge send normal SMS or MMS?
No. Normal SMS and MMS are not beta communication surfaces, even if the physical carrier number can technically support messaging.

### Can Concierge send carrier voice messages or voice notes?
No. Carrier voice-note or voice-message messaging is not a beta communication surface.

### When can Concierge call me?
Concierge can evaluate an owner return when a short decision materially unblocks native work. Current policy, availability, attention context, allowance, and other authority checks still apply.

### Can Concierge keep working after I hang up?
Yes, when the native Codex work remains open. Hangup ends Voice, not necessarily the native work responsibility.

### What is a scheduled recheck?
A scheduled recheck lets supported same-thread Codex work evaluate its current state again later. The recheck must read the current work, authority, and limits.

### Does a scheduled recheck authorize a call?
No. A scheduled recheck grants no call authority and reserves no phone allowance. Any later phone action must pass current checks again.

### What is current context?
Current context is a bounded continuity selection into native Codex history for the next verified owner call. The owner can dismiss the selection.

### Can I edit the current context?
The derived current-context selection is dismissible, not directly editable. Owner-authored context notes are a separate bounded editable surface.

### Does Concierge store my conversation context?
Codex owns the authoritative native conversation context. Concierge does not create a competing semantic transcript, task, or personal-memory database.

### Why does my call transcript repeat messages?
The native App Server can show overlapping partial and final lines in its realtime delegation context, and the current input can appear there again. That is a display/provenance issue, not proof that Concierge sent the request or ran an action twice. Concierge does not keep a second transcript database. If an action appears duplicated, check its operation status before trying it again; otherwise reopen the native thread view and report the call time if the repetition persists.

### What operational data does Concierge store?
Concierge can keep bounded account, phone, routing, contact, policy, allowance, usage, readiness, and continuity-coordination data needed to run the service.

### Is call recording enabled?
Call recording is not enabled by default in the current product. This is not a promise that calls can never be recorded.

### What happens if Codex is offline?
Live phone Voice is unavailable while the required paired Codex computer is offline. Concierge does not replace it with another voice brain. The responsibility remains with native Codex and can continue or recheck when the required native runtime is available.

### What happens if a call result is uncertain?
Concierge does not assume the call failed. It keeps stable operation identity and reconciles authoritative provider state before another consequential attempt.

### What is my phone allowance?
Concierge includes 7,200 seconds (120 minutes) and Concierge Pro includes 60,000 seconds (1,000 minutes) per recurring seven-day window anchored to real service activation.

### How does the phone allowance window work?
Your selected Concierge entitlement sets a bounded owner-visible phone allowance in a recurring seven-day window anchored to real service activation. Unused time does not roll over, and Concierge does not add automatic paid overage at launch.

### What happens when the phone allowance is low?
Concierge stops admitting new allowance-consuming calls at the normal cap. A qualifying already-admitted active call can use the non-reusable finish-current-call period.

### Do I keep my Concierge number?
The product model preserves one Concierge phone identity across target changes. Number ownership and service entitlement remain separate lifecycle facts.

### Can Concierge call emergency services?
No. Concierge does not support emergency calling. Do not use Concierge to contact 911 or another emergency service.

### What types of outreach are prohibited?
The beta prohibits sales prospecting, cold calling, lead generation, unsolicited promotion, campaigns, bulk outreach, political outreach, harassment, and safeguard evasion.

### Are all phone paths fully validated in the current beta?
No. Inbound, outbound, owner-return, full setup, and Windows production paths still have current validation limits. See Current availability and limits for details.

## Glossary
URL: /docs/glossary

### Codex
The current beta operational phone target and native semantic orchestrator for Concierge calls.

### Paired computer
The computer connected to Concierge that provides the current Codex phone runtime.

### Native host
Technical term for the paired runtime host. Consumer procedures normally say paired computer.

### Phone network
The public telephone network used by Concierge calls.

### Owner verification
Setup process that proves possession of the owner's canonical phone number.

### External caller
A caller who does not have verified owner authority for the current call.

### Phone target
The first-party OpenAI surface that owns new Concierge phone communication. Codex is the current beta target.

### Scheduled recheck
A later evaluation of the same supported native Codex work. The recheck does not grant phone authority.

### Phone allowance
Owner-visible Concierge phone time available within the recurring seven-day service window.

### Current context
A bounded continuity selection into native Codex history for the next verified owner call.

## Updates
URL: /changelog

### 2026-08-30 — Agent instructions use progressive disclosure
Category: Improvement
- Live phone guidance now keeps the normal call path concise and loads branch-specific guidance only when needed.
- Normal SMS, MMS, and carrier voice-note fallback remain outside the beta.

### 2026-08-29 — Carrier generation and replay hardening
Category: Reliability
- Inbound call identity now remains generation-exact through routing, native attachment, current context, and usage reconciliation.
- Ambiguous provider effects continue to reconcile instead of using blind retries.

### 2026-08-28 — Owner context controls
Category: Product
- The owner can inspect and dismiss the selected current context.
- Owner-authored context notes remain a separate bounded editable surface.

### 2026-08-27 — Voice-first personal-use boundaries
Category: Security
- Outbound Voice purpose is limited to personal, transactional, individually directed communication.
- Normal SMS and MMS remain outside the beta communication surface.

### 2026-08-27 — Resumable owner phone verification
Category: Reliability
- Accepted and consumed verification states can resume without unnecessary provider rechecks.
- Binding mismatches and terminal rejected states continue to fail closed.

### 2026-08-27 — Same-thread scheduled rechecks
Category: Product
- Supported Codex work can schedule a later same-thread recheck.
- A scheduled wake does not authorize a phone call or reserve phone allowance.

### 2026-08-26 — Phone allowance and finish-current-call behavior
Category: Product
- The phone allowance is 7,200 seconds on Concierge or 60,000 seconds on Concierge Pro per recurring seven-day activation-anchored window.
- A qualifying admitted active call can use a non-reusable finish-current-call period.

### 2026-08-25 — Native Codex Voice lifecycle hardening
Category: Reliability
- Native call startup and attachment use stricter ownership and lifecycle fencing.
- Call teardown no longer implies permission to end durable native work.