TrueDialog

By TrueDialog Inc

Overview

TrueDialog helps users inspect their SMS accounts and channels, find and maintain contacts, and send outbound SMS messages through ChatGPT.

Tools

create_contact

ChatGPT

Create a contact. Either phone_number or email is required. phone_number should be E.164 format (e.g. "+15125551234"). Projected through :class:ContactInfo — see :func:get_contact.

get_account_info

ChatGPT

Get details for an account. Defaults to the authenticated account if omitted. Projected through :class:AccountInfo — see :func:list_accounts.

get_contact

ChatGPT

Get a contact by ID. Defaults to the authenticated account if account_id is omitted. Projected through :class:ContactInfo: drops `createdBy / modifiedBy` (logging metadata) rather than forwarding TD's response verbatim.

list_accounts

ChatGPT

List all accounts visible to the supplied credentials. Projected through :class:AccountInfo: drops the account's `callbackToken (an auth token) and the internal systemAccount` flag rather than forwarding TD's response verbatim.

list_channels

ChatGPT

List all channels (SMS, RCS, email, voice) configured on an account. Use this to discover the channel id you need before calling send_sms. Projected through :class:ChannelInfo: drops the internal `isSystem` flag rather than forwarding TD's response verbatim.

search_contacts

ChatGPT

Search for contacts by phone number or email substring. Projected through :class:ContactInfo — see :func:get_contact.

send_sms

ChatGPT

Send an SMS to one or more phone numbers (raw TrueDialog platform send). NOTE: replies to this send are NOT visible here — TD inbound is push-only into Inbox. For conversational SMS (send AND read the human's reply in a thread), use inbox_sms_send + inbox_get_thread instead, on deployments that enable the Inbox tool pack.

update_contact

ChatGPT

Update an existing contact. Only the fields you supply are changed; pass an empty string to clear phone_number or email (a contact must always keep one of the two). phone_number should be E.164 (e.g. "+15125551234"). This reads the record first and rewrites only the fields you pass, so it needs contact-read permission (Contacts_List or Comms_Hub) in addition to Contacts_Manage, and it is not atomic against a concurrent edit. Projected through :class:ContactInfo — see :func:get_contact. This one is load-bearing: TD's `ContactController.Put returns the raw LinqToDB Contact entity rather than a ReturnContact, so without the projection createdBy / modifiedBy` and any future entity field would flow straight through (PR #42 review).