Human + AI calls
Answer inbound calls with a task you choose, place outbound calls yourself or with AI, and on supported clients hand the connected call between yourself and the model without hanging up.
One account · your devices · your phone lines
Calls, SMS, voice tasks, and device control — on hardware you own.
Attune connects Windows PCs, Android head units, Linux/Docker nodes and SoftRouters to one account. Use your own SIMs for human or AI-assisted calls, live interpreting and SMS; manage connected devices; and let apps or agents use the same line through REST and MCP.
Sign in Android Car Open workspace Get started
Windows evaluation · Android Car · Docker / SoftRouter · Developer API
Windows and Android are evaluation builds; hardware validation varies by release. Carrier airtime, hardware and model API usage are separate from the Attune software subscription.
Communications that stay on your line
Use the same SIM and account from the console, a car screen, or an API client.
Live interpreting
Speak in your language while Attune voices the other language on the phone line. It is consecutive interpreting with visible text and normal model/network latency, not zero-delay simultaneous interpretation.
SMS, history & status
Send SMS through the line you control, keep call/SMS history, export supported recordings, and check whether a call connected or ended and whether an SMS was submitted.
One account, several device roles
Choose the client that fits the hardware you already have.
Windows x64
Local console for EC20-class hardware, direct human calls, AI calling, interpreting, SMS, history and audio-device selection. The current Windows build remains an unsigned evaluation with hardware acceptance still release-specific.
Android Car
A sideload evaluation for aftermarket head units with a phone-style keypad, SMS/history/line views and two-way voice tasks. Its assistant discovers device MCP tools and can use the account line when local board media is unavailable.
Linux, NAS & SoftRouter
Run the Docker device client on x86_64 Linux, NAS or a soft router. Stable device and line identities let the account distinguish the node from display aliases; supported modem hardware remains release-dependent.
Your devices follow the account
Remote access is tied to authenticated users and device identity, not to whichever browser happens to be open.
Workspace & Remote Link
Registered devices appear under the signed-in account with stable UUID identity, online state and device-specific pages. Rename and account-scoped sync stay separate between users; supported clients can expose bounded diagnostics or support actions.
Contacts, records & membership
Optionally sync Google contacts, keep account-linked call/SMS records, and use the same membership across the supported console and communications API. Registration does not start the trial until you explicitly start it.
Authorization before automation
Workspace roles control sensitive device actions. Router provisioning uses a short-lived owner/admin authorization ticket instead of exporting the browser session, and command/write gates stay fail-closed unless a deployment explicitly enables them.
Apps and agents use the same account
No second telephone product is required just because the caller is an app or an AI agent.
REST + MCP
Create an account API key for your own app, or connect supported MCP clients. The communications tools use the SIMs on your Attune seat, while recent_calls and recent_sms let an agent check the result instead of assuming a dial or send succeeded.
Voice tasks on the car screen
The Android Car evaluation opens a two-way voice session, discovers its device MCP tools with initialize/tools/list, and lets the model choose only the tools that device exposes. A started call is not reported as answered until status says so.
Observe the result
Calls and SMS are asynchronous operations. Attune separates “started”, “connected”, “ended”, “submitted”, “pending” and failure states so a client can avoid blind retries when the result is uncertain.
How it works
1. Create your account
Verify an account, then start the eligible 7-day membership trial only when your device is ready, or subscribe from Pricing.
2. Connect a device and line
Use Windows, Android Car, Docker/Linux or a SoftRouter node. Bring your own supported modem/SIM and keep carrier airtime under your own account.
3. Use the workspace, voice or API
Operate from the web/device console, speak a task on Android Car, or use REST/MCP. Each path resolves to the devices and lines authorized for that account.
Questions
What am I buying?
A software membership: account/workspace access, supported device clients, calls and SMS on your own line, records and supported recordings, plus the Communications API. Some desktop/car builds remain evaluations rather than hardware-certified releases.
Does Attune give me a phone number?
No. You keep the SIM, number and carrier relationship. Attune is the software layer that connects that line to your devices, console and API.
Where is my data?
Audio and transcripts stay on the device node by default. Account-linked device state, contacts or records may sync to the service when you enable those features. We do not sell call lists.
Can I send bulk sales calls?
No. Use only numbers and lines you are authorized to contact. Unsolicited marketing campaigns, robocalling and spam messaging are not permitted.
Which hardware is supported?
Support is release-specific. Check the Windows, Android Car and Docker evaluation pages before buying hardware. A matching USB ID or modem family name is not the same as completed hardware acceptance.
Start with the device you already have
Read the setup notes first, connect your own line, then start the trial or membership when the hardware is ready.