AI Employee

👉 Voice AI -> Capturing Secure Keypad Input (DTMF) from Caller 📱
Payments taken during phone calls is my top most priority but I've also been thinking of other use cases such as asking callers to authenticate themselves using their keypad by entering OTP sent by text message to the phone number on file, multi-step verification (e.g., enter postcode, or DOB digits + last 4 of phone number), or a preset secret code on their profile - for secure requests. There are many possibilities.. Multi-level IVR-like flows, but powered by AI context (e.g., “Press 1 to reschedule, 2 to cancel, 3 to speak to an agent”) Numeric field data capture : Enter postcode, date of birth, account number, item quantity or amount (e.g., “Enter the number of units you’d like to order”) Order-related enquiries (press to select order type (e.g., “1 for new order, 2 for existing order”) Important changes to the contact's information, such as date of birth, etc. Enter ticket number or reference ID Mortgage/loan : Enter loan number or last 4 digits of account number Insurance : Enter policy number or claim reference Healthcare : Enter patient ID or appointment reference Enter card number, expiry, and CVV via keypad (with masking for PCI-friendly secure DTMF input). Confirm payment amount by pressing a key (e.g., “Press 1 to approve £36.00”). Select stored payment method (e.g., “Press 1 for Visa ending 42, Press 2 for MasterCard ending 19”) Press a key to confirm terms, disclosures, or agreements Must support retry logic : “That code didn’t match. Please try again.” Fallback : After 3 failed attempts, transfer to a member of staff. Sequential capture : "Enter your 6-digit policy number, followed by the pound key." Inline validation : "That number doesn’t match our records. Please re-enter." Masking & Security : Ensure sensitive inputs (card numbers, PINs) are not stored in transcripts. User Experience : Allow “#” or “*” as end-of-input markers for variable-length entries. Provide clear instructions: “Enter your 6-digit code, then press #.” Short confirmation prompts: “You entered 1234. Press 1 to confirm, 2 to re-enter.” Fallback & Escalation : If keypad input fails repeatedly, offer to send a text message with a link or live agent transfer. Timeout handling: “I didn’t receive any input. Would you like me to repeat the options?”
1
Allow Conversation AI to break long text blob replies into shorter multi conversational message replies
Instead of replying with a long blob of text. Do it more like a human, where they get broken up into shorter sentences sent as separate messages. It's easier to read in things like SMS, Facebook Messenger, IG DMs etc... So AI generates the full reply to the users last response, but then if a setting is toggled on the bot for "Break long replies into multiple shorter messages" it can break that up into multiple shorter messages when sending it to the contact. eg. Instead of sending one message of "Perfect. Here’s what I'm thinking. Let's book you a 9-minute call with Carl, our head coach. He's been building businesses for over 23 years, and I think you'd find the chat really valuable. Carl has a few slots available this week. How does, say, Thursday around 10 AM Sydney time sound? If not, I can offer some other times." It sends it as Message 1: Perfect. (waits to simulate type time) Message 2: Here's what i'm thinking... (waits to simulate type time) Message 3: Let's book you a 9-minute call with Carl, our head coach (waits to simulate type time) Message 4: He's been building businesses for over 23 years, and I think you'd find the chat really valuable. (waits to simulate type time) Message 5: Carl has a few slots available this week. (waits to simulate type time) Message 6: How does, say, Thursday around 10 AM Sydney time sound? (waits to simulate type time) Message 7: If not, I can offer some other times (Waits for contacts reply) Makes it way easier to read for the recipient. And simulates a natural chat conversation. As chat is short messages, not long messages like email.
0
Load More