# Keywords are ops infrastructure.

HOURS, BOOK, MENU, PROMO — keywords are how customers drive your system without learning a new app. Reliable match → multi-step path → human exit when trust requires it.

## Overview

Keyword automation is how local brands, support-leaning social teams, and campaign ops publish always-on entry points. Ranking intent: keyword ops — menu design, conflict avoidance, campaign codes vs evergreen trees, escalation. Different job from comment-to-DM spikes; different job from broadcasts.

## Who runs keyword ops

Local businesses, support-leaning social teams, and agencies that ship evergreen menus clients can staff.

You will recognize this if:

- Your bio or posts publish codes people message you.
- You need multi-step answers, not one canned sentence.
- Staff must take over for exceptions.
- You run time-bound campaign codes alongside evergreen menus.

## Keyword systems rot when menus and promos collide.

One mega-bot with overlapping phrases double-fires and confuses customers.

Dead campaign codes left live break trust when someone messages last month’s promo.

No human exit turns a booking exception into a one-star review written to the bot.

## How to build keyword infrastructure that lasts

Disjoint sets, evergreen vs campaign separation, escalation by design.

### Inventory the questions you answer every week

Those become evergreen menus. If staff types it daily, automate it carefully.

### Assign disjoint phrase ownership

No two live automations should fight for the same words.

### Separate evergreen trees from campaign codes

Campaigns expire. Menus should not die with them.

### Build multi-step only where it changes outcomes

Location pickers, booking links, FAQ branches — complexity must earn its keep.

### Define handoff keywords and situations

HUMAN, AGENT, or escalation rules for when automation stops.

## What keyword infrastructure buys you

Consistency, coverage, and calmer staff inboxes.

### Always-on answers without always-on managers

Core questions resolve while the team serves people in the room.

### Campaign codes that do not poison menus

Time-bound phrases live apart from evergreen trees.

### Fewer double-fires and mystery replies

Disjoint ownership makes behavior predictable.

### Escalation that protects reputation

Humans own the exceptions automation should never touch.

### Shared patterns across locations or clients

Reuse menu structure with local details.

### Entry into capture or nurture when needed

A keyword can start a longer path without a second product silo.

## Keyword constraints

Matching is practical, not magic. Design for humans typing on phones.

- Prefer clear phrases people will actually send.
- Overlapping live triggers create operator pain more often than engine brilliance.
- Messaging windows still apply after the match.
- Menus are not a substitute for staffed support on hard problems.

## Related jobs

- [Lead capture](/en/use-cases/lead-capture)
- [Local businesses](/en/solutions/local)
- [Broadcasts](/en/use-cases/broadcasts)
- [Agencies](/en/solutions/agencies)

## Questions about keywords

### How strict is keyword matching on messy social text?

Matching is designed for practical social text, not compiler-grade tokens. See product docs for exact modes and normalization. Design keywords people will actually type.

### Can one trigger hold a list of phrases?

Yes — lists in the trigger model. Prefer coherent sets (HOURS/OPEN/SCHEDULE) rather than unrelated campaigns fighting one trigger.

### What happens if two live automations share overlapping keywords?

Operator confusion and double-fires. Prefer disjoint live sets. Clear ownership of phrases beats clever overlapping graphs.

### When should a keyword path stop and open the inbox?

Complaints, booking exceptions, refunds, and anything where a canned branch damages trust. Inbox roles exist so automation is infrastructure, not a wall.

### How do local menus differ from campaign codes?

Menus are evergreen ops (hours, booking, FAQ). Campaign codes are time-bound promos. Separate automations and tags so a dead promo code does not break the menu tree.

### Can keywords start lead capture or nurture without a second product?

Yes. After match, free Logic can collect fields, wait, tag, and hand off in the same contact model as other use cases.

## Publish codes. Own the exceptions.

Start free, ship an evergreen menu with a human exit, and keep campaign phrases on a short leash.

[Start free](/en/signup) · [See pricing](/en/pricing)