Engagence

Adds contacts from a pasted list or table: name, phone, email and tags, the same columns Import takes. Answers a preview first: how many are new, how many are already on the list, which tags would be new and which automations would start; the contacts are added on the confirmation. A change that needs the person's approval comes back as a proposal and is not made by this call.

add_contacts_from_text

Enrolments: more time or extra sessions on what this business sells by the period. Adds extra sessions to one active or paused enrolment, used after its own sessions run out and up to a use-by day no later than its last day where it has one, with an optional fee and reason. It applies when the person has asked for it. A change that needs the person's approval comes back as a proposal and is not made by this call.

add_extra_sessions

The business’s group sessions (dated classes customers join). Adds sessions of a service booked in sessions, the same every week: the service, who or where, places and cutoffMin (minutes before the start that joining closes; 0 = up to the start), weekdays, time or times, from, and until or weeks. A change that needs the person's approval comes back as a proposal and is not made by this call.

create_weekly_group_sessions

The business’s group sessions (dated classes customers join). Adds people to one session date: a contact (on a plan or not), or a walk-in who is not saved as a contact, with how many places and whether a place uses their plan or is a single session at the service’s price; places beyond the contact’s own are single sessions. It answers the places booked, what they use and the places left. It refuses a full or closed session, more places than are left or than one booking takes, and a plan with nothing left, naming the single price. The customer is messaged as for any booking; a walk-in who is not saved is not messaged, uses no plan and is not added to the contacts. It applies when the person has asked for it. A change that needs the person's approval comes back as a proposal and is not made by this call.

add_people_to_group_session

The business’s group sessions. Adds places for someone already on a session date, by the id list_session_people gives; each added place is a single session at the service’s price. It answers their places now and the places left. It refuses a full date, a class only plan holders can book, a trial or weekly place, more places than one person may hold on a date, and an id no longer on that date. No separate confirmation is sent. It applies when the person has asked for it. A change that needs the person's approval comes back as a proposal and is not made by this call.

add_places_to_booking

Time off, holidays and closures: a person or space off (resource), or the whole business (scope business). kind off = whole days, or startTime to endTime across the dates; special_hours = open only startTime-endTime those days; extra_hours = an extra shift for one person or space. Dates YYYY-MM-DD in the zone the hours are kept in. Saves one: whoever is already booked inside stays booked, never cancelled, and the answer names those customers.

add_time_off

Asks Meta again about the templates of this account that carry an id from Meta, whatever state each is in (approved, paused, rejected or still waiting for a decision), and returns which statuses changed and how many are still waiting. The status Meta answers for a template is stored on that template, with the reason where Meta rejected it; nothing else on the account changes. A template can also be waiting on this account without having reached Meta: the result says how many of those there are and names them. Nothing can be asked about one of those; sending it to Meta again is what settles it.

check_template_status

Runs the CRM sync now, the Sync now button on the Zoho CRM, Dynamics 365 or Salesforce tab: it reads the saved view; each person in it with a name and a usable number is added, or linked to the contact already there, with the saved tag, and the rest are counted as skipped; it cannot be undone. The result gives the run’s own counts, and a refusal (switched off, no view or tag, not connected, too many runs) comes back in the screen’s words. A change that needs the person's approval comes back as a proposal and is not made by this call.

run_crm_pull

Enrolments: who is signed up to what this business sells by the period, and their fees. Cancels one enrolment that is a request, a trial, active or paused: the customer comes off it, their sessions stop counting and no new fee is recorded; fees already recorded stay, and nothing is refunded. A cancelled enrolment is not reopened; enrolling again starts a new one. It applies when the person has asked for it. A change that needs the person's approval comes back as a proposal and is not made by this call.

cancel_enrolment

The business’s group sessions (dated classes customers join). Cancels one session, with a reason; everyone booked is told. When several match, it asks which. A change that needs the person's approval comes back as a proposal and is not made by this call.

cancel_group_session

The business’s group sessions (dated classes customers join). Cancels this date and every later one of its repeat, with a reason; everyone booked is told. When several match, it asks which. A change that needs the person's approval comes back as a proposal and is not made by this call.

cancel_remaining_group_sessions

Cancels the subscription plan on this account. How the account is billed decides which of two things that means. Where the payment provider bills it: the subscription runs to the end of the period already paid for and is not billed again, after that day the account goes inactive, and a plan change already booked is discarded and does not come back. Where the payment provider does not bill it: the cancellation is recorded from the moment it is confirmed, no money moves, no credits are taken, nothing booked is discarded, and the record itself stops nothing — on an account that is not blocked the AI goes on answering and spending the balance until it runs out or a person here blocks it, and on an account that is already blocked the AI has already stopped and this changes neither the block nor the balance. On the record alone this account is refused its next period of credits — nothing more is granted at its anniversary — and what this platform still gates: AI voice numbers and API keys. Its confirmation states which of the two it is before anything happens. A change that needs the person's approval comes back as a proposal and is not made by this call.

cancel_subscription

Changes one campaign: its name, who it goes to, the message template it will use, the kind or the language. Whatever is not stated is kept as the account holds it; who it goes to is replaced by the people stated, not added to. Somebody the platform cannot reach on the campaign's channel, or who has left the contact list, is set aside, and the result says how many are really on it. The channel is not changed: it stays what the campaign already goes out on. The kind, the language and the template go together: a pairing the campaign builder could not make is refused. A field cannot be emptied and the template cannot be taken off; a blank one is refused. Whether a campaign has been launched is not something this changes. Sending an existing campaign to people is a separate act. Nothing is sent by drafting or changing a campaign — it goes out only when the campaign is launched, and a campaign with no message template on it or nobody on it cannot be launched at all. A change that needs the person's approval comes back as a proposal and is not made by this call.

update_campaign

Changes one contact: their name, number, email address, tags, notes, the channel they prefer or where they live. Only the fields that are stated change, and each replaces the stored value whole; everything else on the contact stays exactly as it is. The tags stated become the contact’s whole tag set, so a tag left out of them is removed: it cannot add a tag or take one off on its own. Either an email address or a mobile number has to remain on the contact. Where a contact came from cannot be changed here. Neither can whether their number or their email address has been checked — but changing either of those clears the check on the one that changed, because a check is about the value it was made on. Where they live is a different thing, and this does change it. A customer on this account is a contact, and their phone number is the number above. A change that needs the person's approval comes back as a proposal and is not made by this call.

update_contact

Enrolments: who is signed up to what this business sells by the period, and their fees. Changes one enrolment that is a request, a trial, active or paused: who attends (newParticipant), its start or end date, its agreed fee and currency, or its notes; only what is stated changes, and nothing is charged or refunded. Weekly dates already booked before a moved start date or after a moved end date are cancelled. It applies when the person has asked for it.

edit_enrolment

The business’s group sessions (dated classes customers join). Changes one session — only what was said of date, time, who or where, places, cutoffMin, note; with anyone booked or a place held, only its note changes. When several match, it asks which.

update_group_session

The business’s group sessions (dated classes customers join). Changes this date and every later one of its repeat — time, who or where, places, cutoffMin, or new weekdays; booked dates keep their time, people and spaces. When several match, it asks which. A change that needs the person's approval comes back as a proposal and is not made by this call.

update_weekly_group_sessions

Changes a person, a space or a shared capacity: its type (the business's own word), whether it is a person, its hours, its capacity, or whether it may be booked by the AI. Only what is stated changes; everything left out stays as it is. Tags are a space's seats and its area only: any other tag is refused and nothing is saved. To change a person or a room is this tool.

edit_resource

What this business sells by the period: a fee per week, month, quarter, year or term, or a pack valid N days, allowing bookings per week, per period or in total, on some or all services. Changes one: it takes the current name in plan and changes only what is stated; active false stops new enrolments, keeps current ones; endsOn is its last day. allowance (0 = unlimited) with allowancePer; a term needs termStartsOn and termEndsOn, a pack validForDays. makeUps true switches make-ups on (makeUpNoticeHours default 24, makeUpExpiryDays default 30, makeUpLimit a period, default the weekly allowance, 0 = no limit); false off; a late cancellation or no-show never earns one. Also: registrationFee, trial (trialPrice, 0 = free), discountOtherPlan, discountOtherParticipant. Fees are recorded, never collected.

edit_customer_plan

Changes a service on this account: its name, how long it takes, the other words customers use for it, the gap before or after it, its price or currency, or whether it is offered at all. Only what is stated changes; everything left out stays as it is. Changing the length changes what is offered from now on and moves no appointment already booked. A service turned off is not offered any more, and the bookings already taken for it keep their place; the result says so only where that is what changed. To change or rename a service is this tool.

edit_service

Changes one automatic tag rule: switches it on or off, changes the tag it writes, or changes what has to be true for it to fire. Something to change: the tag, the signals, or on and off — a call stating none of them is refused. What the call does not state stays as the rule holds it. It takes only a tag already on the account tag list. A rule is a set of signals from a fixed catalog, each named at most once; it fires only when all of them are true. A change that needs the person's approval comes back as a proposal and is not made by this call.

update_auto_tag_rule

Changes one of three integration settings that reach past the Integrations screen. lead_handling: how the leads the AI finds are handled, human approval or automatic, for the business default or for one lead source; automatic sends them straight to the CRM with no human review. msft_booking_calendar: the Microsoft 365 mailbox whose calendar every event the AI confirms is created on, the only calendar Engagence writes to. dynamics_lead_owner: whom new Dynamics 365 leads are assigned to. A setting that is already so is refused, and nothing changes; a change the setting's own door does not allow is refused in that door's words. To change how leads are handled, the Microsoft booking calendar or the Dynamics lead owner is this change. A change that needs the person's approval comes back as a proposal and is not made by this call.

change_integration_setting

Sets the order the custom rules are given to the AI in. The AI is told they are in priority order, so where two of them disagree it may follow the one nearer the top. A change that needs the person's approval comes back as a proposal and is not made by this call.

reorder_custom_rules

Changes the wording of one message template on this account: its body, its header, its footer, its quick-reply buttons, its category, its language, or its name. To change, edit, reword or fix a typo in a template is this tool. Only the parts stated change; the rest stays exactly as it is. To remove the header, the footer or the buttons altogether is this tool too. Wording that uses {{1}}, {{2}} … can be changed, and a new placeholder can be added. New wording stating an hour, a working day, a price, an address, a phone number or a link the account does not hold is refused by name; no other kind of fact is checked. The opening and closing times on the account are the only hours the wording may state; a time inside them that is not an hours claim — a promotion at 2 pm — may be written; a time outside them, or any time or day where the account is silent, is refused. Once Meta holds it, the name, language and an approved category are fixed; other changes go back to Meta for review. Its body is the template’s message text, not a request body: Engagence itself submits the change to Meta’s WhatsApp Business API where Meta holds the template. A change that needs the person's approval comes back as a proposal and is not made by this call.

edit_template

Changes where one appointment stands on the account: it can mark it confirmed, mark it as not confirmed yet, call it off (cancel it), or record whether the person came in. Marking somebody as having come in, or as not having come in, is accepted only on an appointment whose start has already passed and is still standing; once one of the two is recorded the only change left is to the other one, and it cannot go back to being an open booking. A change that is refused is refused in plain words. Calling one off, and recording whether the person came in, each also call off any message still waiting to go out about that booking; the result says which lane it was waiting in, or that nothing was. Calling an appointment off before its time has passed also frees its slot, which is then offered to the people waiting for one, so somebody else may get a message about it. Correcting a mark on a recent booking starts the other mark’s message as well as the first one’s. A change that needs the person's approval comes back as a proposal and is not made by this call.

set_appointment_status

Puts an automation live, pauses it, resumes a paused one, or archives it. To pause, resume, stop or archive an automation, or to put one live, is this tool: a live automation can only be paused, so to turn one off pauses it. The app decides which moves it can make from where it is, and does not archive one that still has people inside. A change that needs the person's approval comes back as a proposal and is not made by this call.

set_automation_status

Maps one bookable person or space to the calendar Engagence reads its free/busy from, or takes that mapping off. A Zoho person, a Zoho login email, an Outlook mailbox, or unlink is required. The provider is asked whether Engagence can read that calendar; one it cannot read is not mapped, and the refusal names the fix. Engagence only reads a mapped calendar; it does not write to it. Undo puts back the mapping that stood before. To link a person or a room to a Zoho or an Outlook calendar, or to unlink one, is this change.

set_calendar_link

Rewrites who the AI is: its identity and manner, in the second person, a short paragraph. Rules, policies and capabilities are not part of a persona: those are custom rules and skills. Asking to change its personality, its persona or how it comes across all mean this paragraph and nothing else. A change that needs the person's approval comes back as a proposal and is not made by this call.

set_ai_persona

Switches what this business’s AI does under a public comment on its Instagram posts: one setting for whether comments are answered at all, one for whether a reply is also posted under the comment itself. Either the answering setting or the public acknowledgment setting is required, and both may be given together. Answering a comment costs 1 credit for each comment interaction. Public Acknowledgment cannot be switched on while Reply to Public Comments is off — the tab disables it there and this tool refuses it — and what may run under a comment is decided outside this app.

set_instagram_comments

Sets which Salesforce user owns the leads Engagence creates in Salesforce.

set_salesforce_lead_owner

Changes the Zoho lead routing: whom the leads the AI finds are assigned to in the CRM, who is invited, and the Zoho calendar new events are created on. At least one of the lead assignee, the invite recipients or the Zoho calendar is required, and any of them may be given together; only what is named changes. A person with no email in Zoho cannot be invited. Every person and calendar is checked against Zoho's live lists, and one that is not on them is refused with the reason. Undo puts back exactly what changed. To change who gets the leads, who is invited or the Zoho calendar is this change.

set_zoho_routing

Switches this account’s two alert settings on or off. To turn one on, turn it off or stop one is this tool: asking to stop being told about every new contact or every new booking means these two settings. Either the new-contact alert setting or the appointment alert setting is required, and both may be given together. What reaches anybody, and whether anything reaches them at all, is not decided here.

set_ai_alerts

Changes how the chat box on this business’s own website looks and what it says first: the name on it, the first message, the grey text in the typing area, whether it is light, dark or follows the visitor’s own device, both colours, the style and the corner it sits in. At least one chat box setting is required, and any number may be given together. The logo is not set here: it is a picture uploaded or a web address pasted on the Chatbot tab. These settings change how the box looks and what it says first, never what the AI answers. The full-width style opens the box by itself on every page load. The small style stops the box opening by itself. The result says whether the copy served close to visitors was dropped by the save; where it was not, a visitor arriving now may see the old look for up to five minutes; somebody whose browser fetched the old one less than a minute ago may keep it for up to ten minutes longer. Colours are six-digit hex values such as #009966.

set_chatbot_settings

Reads one customer’s place in one automation: whether this customer is in the automation or was ever put into it, where the customer is standing in it, why each walk of theirs ended, and what each attempt did. It answers why a customer did or did not get a message from an automation. It carries no message text and no message settings, only what happened. A walk that has left says which leaving it was; reaching the goal is only one of them.

read_contact_automation

Reads how many people are inside one automation and which block each group is waiting on, plus how many have finished, left or failed. Counts only; it names nobody.

read_automation_standing

Enrolments: the weekly times, make-ups and attendance of what this business sells by the period. Clears a customer’s same time every week on one enrolment, on one weekday or on all of them. Its dates already booked are cancelled; the enrolment itself stays. It applies when the person has asked for it. A change that needs the person's approval comes back as a proposal and is not made by this call.

clear_weekly_time

Makes a change proposed earlier in this chat, exactly as proposed, by its confirmationId.

confirm_change

Enrolments: who is signed up to what this business sells by the period, and their fees. Confirms one request to join that the AI took: the enrolment becomes active and this period’s fee is recorded as unpaid, with a registration fee where one applies; nothing is charged. It refuses an enrolment that is not a request, and a request whose plan has ended. It applies when the person has asked for it.

confirm_enrolment

Reads the figures above the contact list: how many contacts there are, how many arrived today, how many have a checked number or address, how many came from each source, and how many a campaign could reach on WhatsApp and on email. The figure for neither identity verified is exactly that — neither one is marked verified — so it also holds the contacts whose number came back invalid or whose address bounced; it is not a count of who has never been checked, and this platform does not hold that count. "Today" is the server's day, not theirs. A contact whose source is anything other than the four the app writes is counted under none of them. Reach is who a campaign may be sent to, which is not the same as having a number: somebody who opted out, and somebody whose tags cannot be read, are counted by neither figure.

contact_stats

Counts how many contacts a set of signals matches right now, before any rule is saved with them. It writes nothing and tags nobody. Where the count was cut short, the real number is at least that many and may be more, and the result says so in words. A rule is a set of signals from a fixed catalog, each named at most once; it matches only when all of them are true.

preview_auto_tag_rule