Can I change my AskVault workspace name after it has been created?

Yes. Go to Settings > General > Workspace name and update it. The workspace slug (used in hosted page URLs) is a separate field and can also be changed independently.

Does changing the AskVault workspace default language change the bot's responses?

Yes for system messages and the widget UI. The bot still responds in the visitor's detected language when auto-detect is on. The default language is the fallback when detection is ambiguous.

Where do I set the timezone for AskVault working hours and SLA?

SLA working hours keep their own timezone in the Help Desk office-hours editor. A separate workspace time zone for analytics and reports (Settings > General > Time zone) is rolling out and not yet switched on; when it is, daily charts, the peak-hours heatmap, date ranges, CSV exports and Resolved today follow it.

General settings

Written by Joseph Russo, Principal Architect, Networks and Tech, AskVault · Reviewed by Allison Chan

Last updated: June 18, 2026 · 2 min read

Fields

Five basic fields:

Workspace name. Display name shown in dashboard, hosted page, transactional emails.
Slug. URL portion (/c/{slug}).
Default language. 35 supported.
Time zone (rolling out). The clock your reports use.
Sender address (rolling out). Send customer emails from your own address, like [email protected]. See Sender address.
Locale. Date/time formatting (US, EU, IN, etc.).

Workspace name

Editable any time. Used in:

Hosted page header.
Widget welcome.
Bot system prompt ({workspace_name} placeholder).
Email subject lines.

Slug

The /c/{slug} URL.

Lowercase letters, numbers and hyphens.
Changing it changes the URL immediately. The old address stops working, so update any links you have shared.

Default language

The bot replies in this language unless visitor message clearly uses another. Auto-detection overrides default per message.

35 languages including English, Spanish, French, German, Hindi, Mandarin, Japanese.

Time zone

Rolling out: not yet switched on. Until it is, reports count days and hours in UTC.

Once it is on, Settings → General → Time zone sets the clock your reports use:

Analytics charts. Daily volume, satisfaction trend and the peak-hours heatmap count days and hours in this zone, and say so on each chart ("Times in America/New_York (EDT)").
Date ranges. A custom range of "Mar 8 – Mar 8" means Mar 8 where your team is, including the 23- and 25-hour days when clocks change.
CSV exports. Daily rows use local dates; conversation exports carry the UTC offset on every timestamp.
"Resolved today" in the Inbox. "Today" starts at your local midnight, not UTC midnight.

If you haven't picked one, the picker suggests your browser's time zone; nothing changes until an admin presses Save time zone. Once it is on, workspaces that set Help Desk office hours will use that time zone for reports until they pick one here. SLA working hours keep their own time zone in the office-hours editor. Only owners and admins can change it.

Locale

Sample formatting:

US: "May 15, 2026" plus 12-hour time.
EU: "15 May 2026" plus 24-hour time.
IN: "15-05-2026" plus 24-hour time.

API access

curl -X PATCH https://api.askvault.co/v1/workspaces/ws_xxx \
  -H "Authorization: Bearer ak_xxx" \
  -d '{"name":"Acme Support","default_language":"en"}'

Limits

Time zone change. No limit; reports re-count from the stored timestamps.
Name change. No limit.

Common pitfalls

Slug change breaks inbound links. The old URL does not redirect. Update links on your site and in emails before you change it.

Time zone mismatch. Analytics show days that end at the wrong hour. Pick the time zone where your team works.

FAQ

Can I change the workspace ID?

No. IDs are permanent. The slug is what's URL-visible and changeable.

Will a time zone change affect past analytics?

Messages are stored with exact UTC timestamps, so nothing is lost. Reports re-count past days in the new time zone the next time you open them.

Was this page helpful?