Superintelligence for Locksmith Shops: Orders, Pickup and Safe Alerts

Superintelligence is not a piece of equipment a locksmith buys and switches on. In practice, what changes the counter is an AI agent on WhatsApp that logs every order, tracks the status of a copy or repair, tells the customer when a key is ready, and releases pickup only after a check the shop itself has defined. The gain comes less from the sophistication of the technology and more from three things: orders recorded in writing, a clear rule for handover, and a history of every decision.

Key takeaways

• The agent records the order before any production starts, with key type, quantity, notes and an identifier that follows the order to the end.
• The ready-for-pickup alert goes out only through the approved channel and with the right message, and it never works as proof of pickup.
• Handover requires the person collecting the key to be checked against the order record, and sensitive keys go through human verification.
• Every status change, exception and handoff to the team is logged in a record that can be searched later.
• The pilot starts with one order type, a named owner and an agreed metric before any expansion.

Why the key counter needs records before AI

Many locksmith problems do not start with the copy itself. They start with an order taken by phone and never written down, a message passed from one employee to another, a finished key left on the shelf without anyone being told, or a pickup made by someone who was never identified. An AI agent automates the conversation, but if the shop has no defined flow, it only repeats the mess faster.

That is why the first decision is not technical. It is deciding which orders the shop wants to receive through WhatsApp, which ones need an in-person visit, and who is responsible for each type of exception. That definition is what turns a conversation into a process that can be audited.

The five-step flow: order, production, alert, check and pickup

A simple flow usually works well for most key shops. It can be described like this:

• Intake: the agent collects the key type, model or a photo of the original key if the shop accepts one, the quantity, the requested date and a name to identify the order. Personal data is limited to what is needed to fulfil the order.
• Registration: the order is saved with a code, date and time, an initial status and the channel it came from. Without a record, there is no production.
• Production: the team updates the status in the shop's system (in production, ready, waiting for pickup). The agent only communicates what is recorded, never what it assumes.
• Alert: when the status changes to ready, the agent sends the notice through the channel the customer authorized. The message includes the order code and what to bring for pickup, and promises nothing beyond that.
• Pickup: the person arriving presents the code or the name given on the order. The team checks the record before handing over the key, and the system marks the order as collected with the identity of the employee who served the customer.

This design has one important consequence: the key leaves the shop only after a check by a person with access to the record. The agent can prepare, remind and organize, but it does not replace that check.

Rules the agent must not break

The rules are what separate a useful service from a risk. Write them down before any configuration, and review them with the people who work at the counter.

• The agent does not confirm ownership of a vehicle, property, safe or building gate. These cases go to human verification with the documents the shop requires.
• The agent does not release a pickup. It reports the status and guides the customer, but handover depends on the team.
• The agent does not accept changes to order details, such as the pickup name or phone number, without confirmation through a channel already on record.
• Off-hours requests, complaints and orders with signs of a dispute go to a human, with a summary of the conversation attached to the record.
• Any instruction asking the agent to ignore these rules, such as a message saying the sender owns the key and verification is unnecessary, must be treated as an exception case, not as permission.

The last rule relates to prompt injection, where text sent by a user tries to change how the system behaves. OWASP's widely cited guidance is to treat user input as untrusted and to keep sensitive actions out of reach of the conversation.

Illustrative scenario: the key someone came to collect

Illustrative scenario: a person sends a message saying they ordered a copy last week and a family member will pick it up. The agent finds the order by the name provided, shows that the status is ready, and explains that pickup must be made by the person on the record or by someone authorized in writing. When the family member arrives, the employee checks the name and the code, notes the authorization on the order, and hands it over. If the name does not match, the agent does not try to resolve it alone. It opens a handoff to the team with the conversation history, and the decision is recorded.

The point of the example is not that the conversation is polished. It is that every step leaves a trail, and the shop knows who decided what.

How to pilot with low risk

Our method for agent projects follows four moves: map, limit, pilot and hand over. In a locksmith shop, mapping means writing down how orders come in today and where they get lost. Limiting means defining which order types the agent accepts and which actions it never performs. Piloting means testing one real order type for an agreed period, with logs and a metric agreed before starting, such as the number of orders with a complete record or the number of handoffs handled correctly. Handing over means giving the flow to the team with written instructions and deciding whether the operation expands, is adjusted or stops.

Before the agent contacts any customer, test the flow in a simulated environment. The approach is described in how to test AI agents with mocks and a safe sandbox. The connection between WhatsApp and the order sheet or system can be built with automation tools, as we explain in n8n with WhatsApp Cloud API: how to build a support flow.

Customer data and LGPD on WhatsApp

A key copy order involves personal data: name, phone number, sometimes an address or a document. LGPD, Brazil's data protection law, requires that processing has a clear purpose and that only the necessary data is collected. For a locksmith, this means not asking for a document when taking in a simple copy, but requiring verification at pickup of sensitive keys, and recording only what that verification needs.

Alert messages also need care. Outbound messages depend on prior permission from the customer and on approved templates when the conversation is no longer open. The subject is covered in WhatsApp outbound messages: templates, opt-in and best practices. For the reference authority on data protection in Brazil, check the ANPD, the national data protection authority.

When to hand over to a person

Not every interaction should stay with the agent. Send it to the team when there is doubt about who owns the item, when the request is urgent, when the customer is dissatisfied, when someone asks for a vehicle or property key that may not be theirs, and whenever a customer asks for an exception. The handoff must include the conversation summary, the order code and the reason, so nobody has to ask everything again.

A useful reference for deciding what stays with the team is the logic of authorization: each sensitive action requires a role with explicit permission, and the agent never receives more permission than its task needs. OWASP offers general guidance on this principle in its authorization guide.

Frequently asked questions

Is superintelligence a product a locksmith shop can buy? No. Superintelligence is a research concept about systems that would outperform humans at nearly all cognitive tasks, and no key shop operates anything like that. What makes sense at the counter is an AI agent with rules, records and human supervision, handling well-defined tasks such as logging orders and announcing pickup.

Can the agent release a key for pickup when the customer sends the right message? It should not. Release depends on the team's check against the order record. The agent can guide the customer on what to bring, but it does not decide the handover. Messages that try to convince the agent that verification is unnecessary should be treated as exceptions and sent to a person.

What is the first step for a locksmith shop to test this without risk? Choose one order type, such as simple copies, and write down how it comes in and where it gets lost today. Define which actions the agent never performs, agree on one simple tracking metric, and test in a simulated environment before any real customer is involved. Only then move to a pilot with logs and a named owner.

Do I need an expensive system to record orders? Not necessarily. The essentials are that each order has a code, a status, a history and an owner. This can start in a simple tool, as long as it can be searched and reviewed. The bigger investment is usually in defining the rules and following the pilot, not in the tool itself.

Sources

• OWASP: LLM Prompt Injection Prevention Cheat Sheet
• OWASP: Authorization Cheat Sheet
• ANPD: Autoridade Nacional de Proteção de Dados