Can AI Receptionist Take Payments?

TL;DR

For Trillet's $49 direct AI receptionist plan, do not build a workflow that asks the agent to take card numbers or charge a caller during the conversation. The public D2C offer is for inbound answering and supported booking, not a published phone-payment or merchant-checkout entitlement. A caller may still volunteer payment details unprompted, so it is not accurate to promise that an AI phone system can “never see” card information. Instruct the agent to stop that disclosure and direct the caller to your approved secure payment method.

What the agent can do is explain an owner-approved deposit policy in general terms, take an appropriate message or booking request, and tell the caller how your team will follow up. Whether a deposit note can be placed in a particular calendar field, whether a booking is confirmed before payment, and whether a link can be sent are details to test in your configured workflow. None should be presented as automatic D2C features.

Does the Trillet AI receptionist process payments?

The current self-serve receptionist pricing page does not promise card capture, payment authorization, a Stripe checkout during a call or an automatic payment link. Do not infer those functions from broader Trillet platform or enterprise capabilities. If your business requires a payment step inside a voice workflow, ask the Trillet team what product, integration and signed scope could support it before advertising that flow to callers.

For a standard D2C call, think of the agent as a reception and routing layer. It can answer approved questions, take a message, and, when a supported calendar is connected and configured, help book an appointment. Email summaries of calls handled by the platform can help the owner follow up. Optional SMS is separately billed; it is not a free payment or booking-confirmation service on every call.

The agent can be your first answer or a busy/no-answer backup, depending on your phone route. Neither mode guarantees it receives every attempt: carrier forwarding, voicemail timing, provider availability and your own configuration matter. Test the real number before relying on any deposit conversation or booking.

How can a deposit handoff work without collecting card details?

Agree the sequence with your team first. A possible example, not a default Trillet automation, is:

The agent states an approved policy: “This service usually requires a deposit. Our team will confirm the amount and send payment instructions through our usual channel.”
The agent gathers only the contact and appointment details necessary for the request. It does not ask for a card number, security code, bank password or account access.
The booking is either requested or made through a connected calendar according to the rules you chose. Decide whether a slot is provisional until payment; do not tell callers it is guaranteed if your process does not hold it.
A person reviews the call summary or appointment and sends the invoice or payment request using the business's existing approved system.
The team confirms the booking under its own payment and cancellation policy.

The old version of this article promised that the AI always writes a deposit note into every booking and holds the slot. The public D2C offer does not establish either detail for every connected calendar. Test what information reaches your calendar and summary, then write the agent's wording around the process that really works. For more on the supported appointment flow, see can an AI receptionist schedule appointments?.

Which calendars and tools can Trillet use?

The published native D2C booking paths are Google Calendar, Cal.com (including Outlook through Cal.com) and GoHighLevel Calendar. A connected calendar can support booking during a call, but the result depends on appointment rules, account access, availability and a successful connection. Test timezones, conflicts, cancellations, payment-dependent holds and the message shown to the owner.

Other CRM or payment tools are not automatically included as managed native D2C connectors. The platform API can support DIY integrations where feasible, but an API key alone is not a payment workflow, compliance assessment or guarantee that your chosen processor can be used during an AI call. If you use Calendly or another scheduler, verify the actual path rather than assuming a native connection or categorically saying no integration could ever be built.

You may choose to send an invoice or payment link yourself after a call. If you configure a text workflow, check consent, destination, content and delivery, and include Trillet's separately metered SMS in the cost estimate. Avoid putting card data in the AI transcript, email summary or free-text calendar notes.

Why is card collection on a recorded call sensitive?

Telephone payments can bring card-data systems and recordings into PCI DSS scope. The PCI Security Standards Council's FAQ says sensitive authentication data such as card security codes must not be stored after authorization in digital audio recordings, even if encrypted. It recommends preventing sensitive data from being recorded where possible. The exact obligations depend on the merchant, processor and implementation; this article is not a PCI assessment.

For an ordinary receptionist call, the simpler instruction is: do not ask for card details; interrupt and redirect if a caller starts reading them out. Use a payment method designed and approved for that purpose. If you need a phone-payment solution, scope the recording, transcript, access, retention, processor and data-flow design with appropriate specialists rather than assuming that an AI feature toggle makes the call safe.

This boundary does not guarantee zero card exposure. A caller can say unexpected things, and some calls may be recorded or transcribed depending on settings. Review your actual call-handling and retention controls. The public Privacy Policy says recordings are typically retained for 90 days; “typically” is not an assurance that sensitive payment data will be automatically redacted or erased on a specific schedule.

Do deposits reduce no-shows when collected later?

They might, but this article cannot support a universal 10% to 20% no-show baseline or a claim that merely telling a caller about a deposit reliably changes behavior. A promised deposit is not a paid deposit. Some businesses require payment before confirming a slot; others invoice afterward; either approach can change how many people book or attend.

Measure your own process. Compare a similar set of bookings before and after a clear deposit policy, recording how many were requested, paid, confirmed, cancelled and attended. Note which callers were lost at the payment step. If you collect after booking, give the caller an honest deadline and explain what happens if the payment never arrives. An AI should not imply that a booking is final when the business's actual rule makes it provisional.

The agent's value may be consistent communication of an approved policy and timely owner follow-up, not a guaranteed reduction in no-shows. A person should own disputes, refunds, exceptions and any sensitive payment conversation.

How much does the receptionist cost when payments stay separate?

Trillet's current direct plan is $49/month for 150 included inbound voice minutes, then $0.20 per additional minute. At 300 minutes in a month, that is $49 plus 150 × $0.20, or $79 for plan and voice usage before optional SMS, phone-number, carrier-forwarding or tax charges. Your payment processor and any invoices remain separate.

The D2C offer has a 28-day money-back guarantee on the plan fee, not a free trial or a guarantee that all usage costs or outside processor fees will be refunded. The initial website-based agent draft can be created in about five minutes; production setup still requires owner review, calendar and carrier configuration, safety boundaries and real-phone tests.

Do not claim that one prevented no-show automatically pays for the month. To model value, multiply the number of incremental completed bookings you can substantiate by their contribution margin, then subtract the plan, voice overage, messaging and staff follow-up costs. A $500 job is not necessarily $500 profit, and the receptionist may not have caused every booking it touched. For a fuller billing comparison, see AI receptionist pricing models explained.

What if a caller wants to pay during the call?

The safest D2C script is short: “I can't take a card payment on this call. Please use the secure payment method our team provides. I can take a message so someone can help you.” The exact wording should match your merchant process. It should not invite the caller to read out a card number, imply a link has already been sent, or promise a confirmed appointment before payment when the system has not confirmed one.

If the caller asks a question about refunds, disputes or a payment problem, route it to a person who can review the account. The AI may capture a minimal callback request, but the published $49 inbound plan does not promise an automatic outbound callback at a selected time. Confirm whether a live transfer option is enabled and test what happens when the destination does not answer.

Frequently Asked Questions

Can Trillet's $49 AI receptionist collect card numbers?

Do not configure it to do so. Card collection and live checkout are not published D2C receptionist entitlements. A caller may volunteer a number, so set a clear instruction to stop and redirect the caller to your secure payment process; do not promise automatic redaction.

Can it tell callers that a deposit is required?

Yes, it can explain an owner-approved general policy, as long as the amount and conditions are current. Check whether the calendar or call summary captures the detail you need, and do not imply payment was taken or the slot is held unless the actual workflow confirms it.

Can it send a payment link?

An automatic payment-link flow is not part of the published $49 D2C offer. Your team can send its own approved invoice or link after the call. Any separately scoped integration should be confirmed and tested before being promised.

What if I use Calendly, Xero or a payment processor?

The native D2C calendars stated publicly are Google Calendar, Cal.com and GoHighLevel Calendar. Other tools may require DIY API work or a separately scoped engagement; do not assume a native managed connection. Keep payment-card data out of unapproved calls and free-text records.

Does the $49 price include SMS and payment fees?

No. The plan includes 150 voice minutes, with $0.20 per extra minute. Optional SMS and any carrier or external payment-processor fees are separate. The 28-day guarantee applies to the plan under its terms, not automatically to outside charges.