Skip to main content
Admin surfaces live under Workspace setup and Settings, which splits into sub-tabs: General, WhatsApp, Voice agent, Emails, Users, API and Billing. Standalone workspaces also get a Forms entry; HubSpot workspaces get a Contact owners entry.

​
Fields registry (Workspace setup)

The registry defines what a contact IS in your workspace: which fields exist, their labels, their type, and their list options. Everything else derives from it: table columns, contact-page fields, form questions, trigger conditions and message variables. Mark a field “use as variable” and [yourfield] resolves in every template. Trigger categories are managed here too; each category becomes a sidebar tab.

​
Who fills a field (standalone)

Standalone workspaces have a Filled by column on every field. It is set to Staff unless you change it, meaning only people write that field. Switch it to Voice agent and the AI caller is allowed to collect and write it during a call — see what the agent collects. The distinction is a guard, not a note to yourself. A call that goes to voicemail still produces a full analysis, filled with the agent’s best guesses, so a staff-owned field stays untouchable no matter what came back from the call.

​
Contact owners

Owners are your reps, the people leads are assigned to. Per owner you set:
  • Working hours, which gate automated WhatsApp sends for their contacts
  • WhatsApp number, the personal line their messages send from
  • Default calling agent, so calls to their leads use the right voice and number
  • Language, which drives template language matching for their audience
Where you set it depends on your mode. Standalone workspaces have no separate owners page: everyone who can sign in is an owner, so their send setup lives on their row in Settings → Users. HubSpot workspaces get a dedicated Contact owners entry in the sidebar, because owners come from HubSpot’s owner directory. They are not Nudge logins, and some of them will never have an account here.
The contact owners table with working hours and default calling agents

​
Numbers and agents

Each channel owns its accounts. Settings → WhatsApp holds your phone numbers with their connection type (personal or Cloud API) and the pacing controls described in WhatsApp. Settings → Voice agent holds your AI calling agents: voice, script, calling hours and pinned outbound number. Settings → Emails holds sending addresses and signatures.

​
Connections and alerts

Credentials live in Settings → Connections: WhatsApp connections, the HubSpot token, and the rest. Secrets are write-only, so once saved you see that a value is set and its last few characters, never the value itself. A value tagged managed was set for your workspace by Nudge and is kept up to date for you. You can still replace it with your own, which stops Nudge updating that field. Connecting an OpenAI or Anthropic key is optional. OpenAI unlocks the writing help in Nudge, such as suggesting a note for a trigger; either one can power the WhatsApp assistant. Both have a model field, and both offer a list read from your own key, so you are only shown models that key can actually use. Leave a model blank and the field shows the one that will run instead. Sync failures reach admins as a notification — bell by default, email if you turn it on. It is one row in the notifications table like any other event; every user picks their own, per event and per channel. See Users and roles. Theming is here too: light, dark, or automatic by local sunrise and sunset.

​
API keys

Settings → API mints keys for the REST API and shows the last 100 API requests with their status and errors.
Nudge autosaves everywhere. If you are looking for a Save button, the change is already saved; watch for the brief “Saved” indicator.