SMS Compliance — GitWorkDone

GitWorkDone SMS Consent Documentation

This page documents how end users consent to receive text messages from GitWorkDone, an AI voice-receptionist product operated by Flow Pulse LLC, doing business as GitWorkDone. It documents the call-triggered, one-time customer-care messaging program.

Last updated: October 3, 2026

Program summary

Program: GitWorkDone Appointment Confirmations — transactional, call-triggered text messages only. Not marketing. Not recurring.

Message types: appointment/booking confirmations and callback requests tied to a completed call.

Frequency: one message per call or appointment. No recurring or scheduled messaging.

Messaging provider: Twilio. Operated by: Flow Pulse LLC, doing business as GitWorkDone. Product: GitWorkDone.

How customers opt in

1
A caller phones a business that uses GitWorkDone's AI phone receptionist.
2
During the call, if the caller requests an appointment or needs a callback, the AI agent may offer one text confirming that request.
3
The AI agent reads the full consent disclosure (see “Consent language” below), including the last four digits of the number supplied by the incoming call, message purpose, message-and-data-rate notice, and HELP/STOP instructions, before requesting consent.
4
The caller must clearly confirm that number and consent to the text. If the number is wrong, the caller requests a different destination, or the answer is not a clear yes, no message is sent.
5
Consent is logged with the call recording/transcript, call timestamp, and the phone number the caller called from, as proof of opt-in.
6
After the call ends, at most one transactional SMS acknowledging the appointment or callback request is sent to the number the caller called from. Urgent care details are not included.

No message is ever sent to a number that has not just completed a live, verbally-consenting call with a GitWorkDone-powered agent.

Consent language (verbal script)

The exact script the AI voice agent reads aloud and must receive affirmative consent to before sending any text message:

AI Agent: “GitWorkDone can send you one text confirming we received your request from this call. Message and data rates may apply. Reply HELP for help or STOP to opt out. Program details are at gitworkdone.com/sms-consent and the privacy policy is at gitworkdone.com/privacy. We can send it to the number you called from, ending in [last four digits]. Is that the right number, and would you like that one text, yes or no?”
Caller: “Yes please.”
AI Agent: “Great, we'll send that text over shortly.”

Consent to receive a text message is not a condition of receiving service from the business the caller called. Callers who decline are still fully served by the AI receptionist; they simply will not receive a text.

Sample messages

[Business Name]: We received your request from today's call. Questions? Call [business_phone]. Reply HELP for help, STOP to opt out.

Hi [first_name], this confirms your appointment with [business_name] on [date] at [time]. Call [business_phone] if you need to reschedule. Reply HELP for help, STOP to opt out.

Keyword handling

HELP

GitWorkDone: For help call [business_phone]. One-time call confirmations only. Reply STOP to opt out.

STOP

Twilio handles the carrier opt-out confirmation. Fennlo also suppresses this number from future application messages.

Subscribers can reply STOP at any time to unsubscribe and HELP for assistance. Message and data rates may apply.

Policies & contact

Full program terms appear in our Terms of Service (see “GitWorkDone SMS Text Alert Program”), and our data practices are described in our Privacy Policy (see “GitWorkDone SMS Text Alerts & Mobile Data”). Mobile opt-in data and phone numbers collected through GitWorkDone are never shared with third parties or affiliates for their own marketing purposes, and are never used for marketing messages.

Questions about this program: support@gitworkdone.com. Flow Pulse LLC, doing business as GitWorkDone, Atlanta, Georgia, United States.