Hello, are you still open and can I book for tomorrow?
← All integrations
CLAUDE · AUTOREPLY AI · YOUR MOBILE NUMBER
Connect Claude to the SMS on your own mobile.Helpful replies, sent from your real number.
Connect your own Anthropic API key, define how Claude should answer and assign a reply mode to each Android phone. Claude prepares replies to eligible incoming SMS using the right conversation history. You approve each draft or let the connected mobile send it automatically.
✓YOUR OWN NUMBERReplies leave through your connected mobile
✓ONE ROLE PER MOBILEDifferent instructions for different teams
✓YOU KEEP CONTROLHuman approval or automatic sending
Your support mobileClaude reply mode active
Claude reads this contact’s conversation context
Hi! We close at 19:00. I can help prepare your request for tomorrow. What time would suit you?
Customer SMS→Claude + your rules→Your mobile reply
LESS WAITING. MORE USEFUL CONVERSATIONS.
Let your mobile handle the repeatable part without losing your voice.
AutoReply AI is built for a practical result: receive an SMS, understand its context and produce the next useful answer from the right mobile.
Customers receive a useful answer even when you are busy.
Handle recurring questions, first responses and simple qualification without leaving every sender waiting.
Every mobile follows the instructions you define.
Set the role, tone, facts, escalation rules, schedule and signature once, then reuse them for every eligible conversation.
The conversation continues from the number customers know.
Replies are queued to the connected Android phone and sent through its SIM, so the exchange stays attached to your real mobile number.
Start with approval, then automate when you are confident.
Review proposed replies, refuse unsuitable drafts with a reason and move trusted situations to automatic sending.
FROM FIRST SMS TO A CONTROLLED REPLY
Five steps to put an AI receptionist behind your real mobile number.
Begin with one phone and human approval. Once the instructions and replies are reliable, automatic sending can take over the situations you trust.
- 01
Connect the mobile
Pair an Android phone with SMSMobileAPI. In the mobile app, explicitly enable and synchronize received SMS so new messages can enter the automation.
- 02
Choose Claude and create a mode
Select Claude as the AI provider, add your own Anthropic API key privately, choose a supported Claude model and describe the job and safeguards for this phone.
- 03
Assign the mode to a mobile
Choose which connected mobile uses which mode. A sales phone, support phone and booking phone can each behave differently.
- 04
Choose the decision path
Require human approval for every draft, or allow replies to be sent automatically when the workflow is ready.
- 05
Monitor and improve
Review reply history, decisions, sending status, token usage and the exact amount billed to your AI balance.
CLAUDE, CONNECTED TO YOUR REAL MOBILE
Use your own Anthropic key and keep control of every SMS.
Claude is available as a provider for AutoReply AI. Add a valid Anthropic API key in the dashboard, select a supported Claude model and save the mode for a connected Android phone.
Your Anthropic key
The key is configured privately in the dashboard. Anthropic bills model usage under your own provider account.
Your reply rules
Define the role, tone, operating hours, excluded numbers, signature and when a human should take over.
Your sending phone
SMSMobileAPI queues approved or automatic replies to your connected Android mobile. The SMS leaves through its SIM and number.
ONE ACCOUNT. SEVERAL SPECIALIZED MOBILES.
Give each connected phone the job it is supposed to do.
A named AI reply mode contains its own instructions, selected model, schedule, signature, exclusions and decision path. Assign one mode to the sales phone and another to support, bookings or field operations.
- ✓Sales mobile: qualify a prospect and collect the next useful detail.
- ✓Support mobile: answer approved questions and escalate exceptions.
- ✓Booking mobile: handle opening hours and collect appointment preferences.
Sales mobileDevice reference · A17
Lead qualificationCustomer careDevice reference · B04
Support assistantBooking mobileDevice reference · C12
Appointment deskAUTOMATION WITH GUARDRAILS
You decide who receives a reply, when it runs and whether a person approves it.
Every mode can be strict, flexible or completely manual. The system is designed to progress from supervised assistance to dependable automation.
Named AI modes
Create several reusable behaviors and edit them whenever your business changes.
Per-mobile assignment
Attach the right mode to every connected mobile, including its name and device reference.
Days and schedules
Reply all the time or only on selected days and between the hours you define.
Approval workflow
Approve, archive or refuse a draft without losing the original incoming SMS.
Excluded contacts
Add named phone numbers that must never receive an AI-generated reply.
Short-number protection
Service senders and short numbers are excluded from automatic replies.
Automatic signature
Add a clear signature to every AI-assisted reply when you want recipients to recognize the service.
Complete audit trail
Keep the generated text, decision, sending state and customer-visible billing together.
Human approval
AI prepares the answer. A person approves, archives or refuses it before anything is sent.
Open the approval queue →Automatic sending
Eligible replies are sent through the assigned mobile without waiting for manual action.
Configure automatic replies →Private contextContact + mobile + modeOnly sent replies continue the memory
A SEPARATE MEMORY FOR EVERY CONVERSATION
The right history follows the right contact—and nobody else.
Context is isolated by the correspondent’s number, the mobile that received the SMS and the AI mode assigned to that mobile. This lets the assistant remember a name or an earlier question without mixing conversations between customers, teams or roles.
What becomes memory?The incoming conversation and replies that were actually sent. Pending, refused, archived or failed drafts do not become part of the ongoing exchange.
FROM A SIMPLE ANSWER TO A COMPLETE FIRST-LINE SERVICE
Use the same connected mobile for very different business outcomes.
After-hours reception
A customer asks whether you are open. The phone answers with the correct hours and explains when a person will be available.
Lead qualification
A prospect requests information. The sales mobile asks the next useful question and keeps the exchange moving until a salesperson takes over.
Appointments and bookings
Answer common availability questions, request the missing details and clearly escalate any request that needs manual confirmation.
Field service
A technician’s mobile can acknowledge a request, collect the address or reference and prepare the next step while the technician is working.
Customer support
Resolve known questions from approved instructions and route sensitive, uncertain or exceptional cases to a human.
Several brands or teams
Give each connected mobile its own vocabulary, role, working hours, exclusions and signature from the same account.
VISIBLE COSTS. NO GUESSWORK.
Know what every generated reply costs.
A dedicated AI balance keeps the service separate from your normal subscription. The reply log shows the customer-visible charge and usage for each generated answer.
BASE PLATFORM CHARGE$0.005per generated reply
Claude requires your own Anthropic API key. Anthropic bills model usage separately; your mobile operator may also charge for SMS under your plan.
BEFORE YOU ACTIVATE IT
Three essentials keep automatic replies reliable.
The phone is the communication endpoint. It must remain connected and authorized for the data that powers the feature.
- 1Enable received-SMS synchronization
In the Android app, explicitly allow received SMS to be synchronized. Without this, the service cannot see a new message to answer.
- 2Keep the mobile available
Maintain Internet access, SMS permissions and reliable background operation for the SMSMobileAPI app.
- 3Test with human approval
AI can make mistakes. Validate the complete loop with messages you control before enabling automatic sending.
PRACTICAL QUESTIONS
Understand the feature before it answers the first customer.
AutoReply AI helps with repeatable conversations. Keep a person responsible for sensitive decisions, unusual requests and situations where certainty matters.
Does the reply come from my own mobile number?
Yes. The reply is queued to the connected Android mobile and sent through its SIM and mobile number. Your mobile operator may still charge for SMS according to your plan.
Can I keep a human in control?
Yes. Human approval can be required before sending. The approval queue lets you approve, archive or refuse a draft and record why it was refused.
Can different mobiles perform different jobs?
Yes. Create several named AI reply modes, then assign the appropriate mode to each connected mobile.
Does the AI remember previous messages?
Yes. Conversation context is isolated by contact number, connected mobile and assigned AI mode. Only replies that were actually sent become part of the continuing conversation memory.
Can I prevent replies to specific numbers?
Yes. Every mode can contain several named excluded numbers. Short numbers and service senders are also protected from automatic replies.
Can replies run only outside business hours?
Yes. Select the active days and hours for each mode, or allow it to operate continuously.
Do I need an Anthropic API key to use Claude?
Yes. To use Claude for AutoReply AI, enter your own valid Anthropic API key in the dashboard and select a supported Claude model. The SMSMobileAPI managed Claude connection is not currently available.
What does a Claude-generated SMS reply cost?
SMSMobileAPI charges $0.005 for each generated reply when you use your own provider key. Anthropic bills model usage separately to your Anthropic account. Your mobile operator may also charge for the SMS under your plan.
What must remain active on the phone?
The Android phone must stay connected, have the required SMS permissions and allow the SMSMobileAPI app to operate reliably in the background. Received-SMS synchronization must be enabled in the mobile app.
Can AI make mistakes?
Yes. AI can misunderstand a message or produce an unsuitable answer. Begin with human approval, write precise instructions, exclude sensitive contacts and escalate important decisions to a person.
YOUR MOBILE IS ALREADY WHERE THE CONVERSATION HAPPENS
Give it a clear role, a private memory and the ability to answer.
Create your first AI reply mode, assign it to a connected mobile and begin safely with human approval.
