Four groups can see parts of your AI teammate's work. You and your staff come first, followed by the Hey Button team that configures it. Model providers process the text of each reply they write, and your customers see only the messages sent to them. This post examines each point where information moves through the system; you can then determine who sees what before any customer message is handled.
Who can see your AI teammate's work?
Several distinct groups can access the work, and you are, unquestionably, the first among them. The table below describes what each group can view and explains how that access is established.
| Viewer | What they can see | How their access is set |
|---|---|---|
| You and your staff | Portal activity, drafts, and approvals | Your account and the people you invite |
| Hey Button team | Setup details and ongoing configuration work | Part of the service, so ask which people perform this work |
| Model providers | The text of each request required to produce a reply | Each provider's own data policy, which you can request in writing |
Hey Button runs on OpenClaw, an open automation framework, and models such as Claude and GPT answer requests through that framework. Hey Button does not operate a proprietary model of its own. Consequently, every customer message you process passes to an outside provider as a necessary component of generating the reply. Treat this arrangement as you would any ordinary vendor evaluation, and request each provider's current written data policy before you connect a customer channel.
The Hey Button team configures the teammate during setup. That process begins with an intake conversation regarding how work arrives and which tools your business already uses. The team additionally adjusts the teammate over time as your operations change. Because that ongoing work requires access to the configuration, you should inquire which individuals perform it and precisely what they are able to open.
What does the client portal show you?
The portal functions as your principal window into the day-to-day activity of the teammate. A useful record displays the customer's original message, the rule the teammate applied, and the draft it prepared. A bare entry that reads "replied to customer" reveals very little about whether the underlying decision was sound or appropriate.
During the first several weeks, review a representative sample of entries each morning; look carefully for three distinct patterns. Watch for requests the teammate returned to you. Watch for messages that reached a customer only after your explicit review, and for any action you did not anticipate. Handoffs that appear correct indicate that your rules function as intended. An unexpected action signals that a rule requires tightening before the next customer message is processed.
After you modify a rule, read the next several entries to confirm that the revised rule behaves as you intended. A teammate that no one reviews can drift from the manner in which your business operates, even when it started with precise instructions.
How do access levels change who sees what?
Access level does not alter what you are able to see. It determines only what the teammate is permitted to do without your direct involvement. Hey Button offers three distinct levels. Each one establishes a different boundary between the teammate's autonomous work and the customers who depend on your business.
Under read-only access, the teammate observes incoming messages and organizes them into a structured view for your staff. Because it does not reply to anyone, customers hear exclusively from you or your team. This level suits a business that requires a verified picture of its inbox before it delegates any drafting responsibility.
Under draft-and-approve access, the teammate writes replies and then pauses. A person reviews each draft and must approve it before anything is transmitted to a customer. Customers therefore see only text that a responsible individual has accepted. Numerous owners begin at this level because it lets them evaluate the quality of the writing before any of it reaches a customer.
Under full access, the teammate sends messages independently, but only within a scope that you defined in advance. Spending decisions, sensitive account changes, and similar matters remain governed by the approval rules you selected. Full access widens the lane in which the teammate operates, yet it does not remove the rules that keep that lane safe.
Consider an illustrative lawn care company located in Auburn, Indiana; this example is an illustration rather than a documented customer. The owner selects draft-and-approve access for quote requests; on a Saturday afternoon, an inquiry arrives asking for pricing on a spring cleanup. The teammate organizes the message, identifies the missing information, and drafts a reply requesting the property address along with several photographs of the yard. The owner reviews that draft on Monday morning and approves it, so nothing leaves the business before that approval occurs. For a more detailed comparison of the three levels, read read-only, draft-and-approve, or full access.
Button Block, the company behind Hey Button, is based in Auburn, Indiana; Northeast Indiana owners who want to see these settings in their own inbox should begin with the questionnaire at the end of this post.
What do your customers actually see?
Customers see the messages sent to them, delivered through the same channel they originally used to write. They never see your approval queue, your internal notes, or your rule history, because those records belong entirely to your business. Since a customer receives only a single message, the accuracy and tone of that message deserve your first and most careful attention.
Observe closely for replies that sound certain about matters you have not yet decided. Pricing exceptions, availability on a particular day, and warranty terms represent common examples. A reply can read as polished and professional while still promising something your business cannot actually deliver. Before the teammate handles a topic, write down the precise answer you want, then compare its drafts against that written standard.
Review the first twenty customer-facing messages in their entirety. After that initial period, sample a small number each week and evaluate both accuracy and tone. A reply that reads like a generic form letter can damage customer trust even when each individual fact it contains is correct. Customers frequently judge a business by the feel of a single conversation.
Which accounts should you connect first?
Commence with the least sensitive channel that still produces meaningful, observable work, for example a shared inbox that handles quote requests or appointment questions. Before you connect any account, sort it into one of three categories:
- Public information: business hours, service areas, and general questions that your website already answers.
- Customer-specific details: quotes, schedules, and job notes that belong to individual people.
- Money and formal commitments: anything that moves funds or changes a binding promise.
Most owners permit the teammate to operate within the first category. They widen its access to the second category only after its drafts consistently require minimal editing. They maintain the third category behind approval for a considerably longer period. Connect one channel at a time, so that when a problem appears, you can identify its source with confidence rather than guessing.
What changes when a second person joins the account?
Adding a second person alters the approval path, but it does not alter the underlying teammate. Before you invite anyone, decide who approves drafts, who may change rules, and who may only observe. Document that division of responsibility on a single page. The page should name a reviewer for each queue and establish a time limit for drafts that wait for action. Without a named reviewer, drafts can remain unanswered for days, because each person quietly assumes that a colleague will handle them.
Examine your own working habits as well. An owner who approves drafts from a phone while driving a work truck may approve an incorrect price without reading the message closely. Establish two short review windows each day, and approve drafts during those windows rather than whenever a notification happens to arrive. Deliberate reviews catch considerably more errors than reflexive ones.
Which messages should stay away from the teammate?
Certain messages require a person from the very first contact; a dispute, a complaint involving an injury, and a refund request are common examples. Ask the Hey Button team how your setup can direct those topics to a designated staff member before any draft gets written. Then ask the team to demonstrate the routing with a sample message, and confirm the destination yourself before you depend on it.
Maintain the list of sensitive topics short enough that a staff member can read it and comprehend it in roughly one minute. A lengthy list tends to be ignored in practice; review the list monthly, and examine the messages the teammate handled without a handoff. When a message in that group should have reached a person, adjust the rule accordingly. That adjustment is ordinary tuning, and it does not indicate that the tool has failed in some fundamental way.
When does this setup not fit your business?
Some practices handle records governed by strict confidentiality obligations. Those practices may need to restrict the teammate far more narrowly than an ordinary retail or service business would. Some owners cannot dedicate time to review drafts every single day. For those businesses, read-only access or a tightly limited scope may represent the most responsible choice. Certain messages, particularly those carrying emotional or legal weight, may be better handled by a person from the beginning.
Approval additionally carries a real cost that deserves to be stated plainly; every draft awaiting review delays the customer's answer. If your customers expect a response within minutes, plan your approval windows in advance. Decide deliberately which urgent categories of messages should bypass the queue and reach a person immediately.
The underlying trade-off is simple to describe and considerably harder to live with. More review produces slower replies, while less review increases the probability that an error reaches a customer. Choose a point on that spectrum intentionally and write your choice down. Revisit it after the first month of operation, when you will have enough evidence to judge whether the original choice was appropriate.
What should you ask before you commit?
Bring a short written list of questions to the intake conversation; you are not testing the Hey Button team by doing so. You are ensuring that every answer you depend on exists on paper before any system touches a customer.
Ask these questions directly:
- Which messages and business records will the teammate read, and which categories remain entirely outside its reach?
- Where are conversations and internal notes stored, and how long do they remain there before deletion?
- Which named individuals approve drafts, authorize spending, and approve changes to the rules?
- How can I review the complete message history of one customer from beginning to end?
- How do I remove access entirely, and what happens to the work the teammate has already logged?
Ask about cost in writing as well, because verbal estimates are notoriously difficult to enforce. Identify every software subscription and usage charge before you commit, and sign only when each line matches a number you can verify on paper. Finally, inquire how the team will notify you about configuration changes before they take effect. A change you review in advance is far easier to evaluate against your understanding of the business. A change you discover afterward may already have affected a customer.
Hey Button configures each teammate around your actual operational workflows, with approval rules you select before anything reaches a customer. Start the Hey Button questionnaire, and bring your written question list along with your preferred access level to the conversation. Allow the teammate to earn wider access gradually, one clean and well-documented week at a time.
Frequently Asked Questions
- Can my customers see my internal notes about them?
- No. Customers see only the messages sent to them. Your approval queue, internal notes, and rule history stay inside your business. If a customer asks for a copy of information you hold, handle that request yourself under your privacy obligations.
- Does a customer need to know a teammate wrote the reply?
- Not automatically. Whether to disclose that automated help was used is your decision, and you should settle it before setup begins. A plain, accurate sentence is easier to defend than a reply you later have to explain. Choose the wording once, then use it on every channel.
- Can I lower the access level after I have started?
- Yes. Reducing access is the safer step when a rule behaves unexpectedly. Return to a stricter level while you find the cause, then raise access again only after a sustained run of clean drafts. Record each change and its reason.
- Do I need a written agreement before setup begins?
- Yes, ideally. Put the scope of access, the data handling terms, and the cost in writing before setup starts. Verbal promises are hard to verify later, while a written scope gives you a standard to measure the work against.
- What should I do when the teammate makes a mistake?
- Name one person to log every mistake you find. Send each example to the Hey Button team with the customer's original message and the answer you wanted. That lets the team correct the underlying rule instead of patching individual replies.
Hey Button
Want a teammate that handles this for you?
Answer a few questions about your business and Hey Button will show you what an AI teammate would take off your plate, with you approving anything that goes out.




