Ava MessengerAva Messenger
Ava Messenger 介面導覽Ava Messenger interface tour
下面是 Ava Messenger 登入後的畫面。點左邊的選單或上方的帳號選單,右邊會換成那一項的說明。左側選單會隨著「目前選到帳號還是 Campaign」而不同 —— 可以用上方兩個按鈕切換看看。Below is what Ava Messenger looks like after you sign in. Click the left menu or the account selector at the top and the right side switches to that item's explanation. The left menu changes depending on whether an account or a campaign is selected — try the two buttons above it.
帳號選單(頂部)Account selector (top bar)
這是整個畫面最重要的開關。點上面的帳號選單試試看(裡面是假資料):This is the most important switch on the screen. Try clicking the account selector above (it's filled with sample data):
| 操作Action | 會發生什麼What happens |
|---|---|
| 滑鼠移到帳號上Hover an account | 右邊展開這個帳號底下的 Campaign。只會列出啟用中的 Campaign,停用的不會出現。Its campaigns open on the right. Only enabled campaigns are listed; disabled ones don't appear. |
| 點帳號Click an account | 只選到帳號這一層 → 左側換成帳號選單。Selects just the account → the left side switches to the account menu. |
| 點 CampaignClick a campaign | 選到帳號 → Campaign → 左側換成 Campaign 選單。上方會顯示「帳號 / Campaign」。Selects account → campaign → the left side switches to the campaign menu, and the box shows "Account / Campaign". |
| 選完之後After choosing | 會回到首頁,不會停在你原本看的那一頁。You're taken back to the home page, not kept on the page you were viewing. |
| Search account | 打帳號名稱來找帳號(只搜帳號,不搜 Campaign 名稱)。Type an account name to find it (searches accounts only, not campaign names). |
| 灰色小標題Gray headings | 帳號會依名稱「 - 」前面的字自動分組,例如「Acme - Auto」和「Acme - Home」都在「Acme」底下。Accounts are grouped automatically by the text before " - " in the name — e.g. "Acme - Auto" and "Acme - Home" both sit under "Acme". |
| Create New Account | 建立新帳號。只有部分角色看得到,而且要先綁定 Google 才按得了(見下方說明)。Creates a new account. Only some roles see it, and you must link Google first (see below). |
建立新帳號前,要先綁定 Google。沒綁的話,Create New Account 按鈕是灰的,下面會出現「If you want to create a new account, Please click here to link to google first.」,點 here 就會去 Google 授權;帳號列表頁的建立按鈕也一樣是灰的。綁定也可以從右上角的使用者選單 → Profile → Google → Link。綁好之後,按鈕旁顯示 Linked。
為什麼要綁:建立帳號的人會成為這個帳號的 Account Owner,之後這個帳號建立 Dialogflow 機器人時,會用 Owner 綁定的 Google 授權去 Google 雲端開專案。
只有建立「帳號」需要綁 Google;在 Users 頁新增、邀請使用者不需要。Link Google before creating an account. Without it, Create New Account is gray and a note appears: "If you want to create a new account, Please click here to link to google first." — clicking "here" opens Google authorization. The create button on the account list page is gray too. You can also link from the user menu (top right) → Profile → Google → Link; once linked it shows Linked.
Why: whoever creates an account becomes its Account Owner, and when that account later creates Dialogflow bots, the Owner's Google authorization is used to open projects in Google Cloud.
Only creating an account needs Google; adding or inviting users on the Users page doesn't.
「找不到某個選單項目」最常見的原因不是權限,而是選錯層:例如想改 Campaign 的轉接設定,卻停在帳號層,看到的就會是帳號的 Settings。The most common reason for "I can't find that menu item" isn't permissions — it's being on the wrong level. For example, if you want a campaign's transfer settings but you're on the account level, you'll see the account's Settings instead.
使用者選單(右上)User menu (top right)
顯示目前登入的人。點開可以登出。Shows who's signed in. Open it to sign out.
Profile 區塊(有外部整合權限的角色才看得到):有 Google、Facebook 兩列,沒綁的顯示 Link,點下去走授權;綁好的顯示 Linked。要建立新帳號,得先在這裡綁 Google(見帳號選單的說明)。一個 Google 帳號只能綁一個使用者,所以常見兩種錯誤:
・按 Link 後出現「Please link to google email which is not linked to this account yet. Or directly login from google SSO.」:這個 Google 帳號已經綁在某個使用者身上。換一個 Google 帳號,或直接用 Google 登入那個使用者。
・用 Google 登入時出現「Please link to google email which is not linked to other accounts yet.」:同一個 email 的使用者已經綁了另一個 Google 帳號。Profile section (only roles with the external-integration permission see it): rows for Google and Facebook. Unlinked shows Link, which starts authorization; linked shows Linked. You must link Google here before you can create a new account (see the account selector). A Google account can be linked to only one user, so two errors are common:
・After pressing Link: "Please link to google email which is not linked to this account yet. Or directly login from google SSO." — that Google account is already linked to some user. Use a different Google account, or sign in to that user with Google directly.
・When signing in with Google: "Please link to google email which is not linked to other accounts yet." — the user with that email already has a different Google account linked.
目前登出只會清掉這台瀏覽器上的登入狀態,不會通知系統讓登入失效(已知待辦,見 LT672)。Signing out currently only clears the sign-in on this browser; it doesn't tell the system to invalidate the session (known to-do, see LT672).
Dashboard
/Last Month Call Stats
⤢2| Campaign | Calls | Transfers |
|---|---|---|
| Spring Outreach | 1,240 | 312 |
| Renewal Reminder | 860 | 198 |
Weekly SMS Replies
⤢▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
帳號層的首頁是一張張「報表卡片」,這頁沒有標題列。卡片的排列、寬度、高度都是之前編輯儲存下來的。The account home page is a grid of report cards with no page title. Their order, width and height are whatever was last saved in edit mode.
- 2
每張卡片右上角可以全螢幕看那份報表,再按一次離開。Each card's top-right button shows that report full screen; press it again to exit.
- 3
卡片原本對應的報表被刪掉時,會顯示「Report Has Been Removed.」,不是載入失敗。If the report a card points to was deleted, it shows "Report Has Been Removed." — it's not a loading failure.
- 4
右下角的圓形按鈕是「Edit Dashboard」(只有部分角色有)。編輯時每張卡片要填 Name、Report、Column Span(6–24)、Column height(300–1000),下面有「+ Add Report」;按同一顆鈕儲存,旁邊的 ✕ 取消。The round button at the bottom right is "Edit Dashboard" (some roles only). In edit mode each card takes a Name, Report, Column Span (6–24) and Column height (300–1000), with "+ Add Report" below; the same button saves, the ✕ next to it cancels.
沒有 Dashboard 權限的人,打開帳號層首頁會是一片空白;如果頂部已經選了某個 Campaign,則會被自動帶到那個 Campaign 的 Call Performance Stats。People without Dashboard permission see a blank account home page; if a campaign is already selected at the top, they're taken to that campaign's Call Performance Stats instead.
Campaigns
/accounts/{aid}/campaignsCampaign List ⓘ
1ImportCreate| Name | Created At | Last Modified At | Owner | Status | Operations |
|---|---|---|---|---|---|
| Renewal Reminder (ID: 202) | 03/02/2026 10:15 AM | 09/12/2026 04:40 PM | Demo Owner | Enabled | EditDelete3 |
| Spring Outreach (ID: 201) | 02/14/2026 09:00 AM | 05/01/2026 11:20 AM | Demo Owner | Disabled 4 | EditDelete |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
Create 會開三個步驟:Campaign Info(Name、Default Language 英文 / 西班牙文、Default Timezone)→ IVR Settings → Conversation Settings。Import 是用檔案批次建立:先按 Verify 檢查,過了才能 Import。這兩顆只有部分角色看得到。Create opens three steps: Campaign Info (Name, Default Language English / Spanish, Default Timezone) → IVR Settings → Conversation Settings. Import creates campaigns in bulk from a file: press Verify first, and only then Import. Only some roles see these two buttons.
- 2
可以只看 Enabled 或 Disabled 的 Campaign,預設 All。Filter to Enabled or Disabled campaigns; the default is All.
- 3
Edit 只能改名稱和啟用狀態。Delete 會先確認:Campaign 從清單消失,但歷史資料會保留。Edit only changes the name and enabled status. Delete asks first: the campaign leaves the list, but its history is kept.
- 4
灰色的列是 Disabled 的 Campaign。停用的 Campaign 也不會出現在頂部帳號選單裡。這張表沒有分頁,往下捲就能看到全部。Gray rows are disabled campaigns — they also don't appear in the top account selector. The table has no pages; scroll to see them all.
Conversations
/accounts/{aid}/conversationsConversation Filters
20 / 135 Conversations
🔔↻2(555) 010-0001
Opt-out☏3@Demo Agent4Journey State 7
▲ 模擬畫面(假資料)。實際是四欄:篩選 | 對話清單 | 對話內容 | Journey State。▲ Mock screen (sample data). The real page has four columns: filters | conversation list | chat | Journey State.
- 1
Show 預設是「Has Replies」:只列出聯絡人有回覆過的對話。「對話不見了」「數量比預期少」時先把它改成 All。其他篩選:Assignee、Link(點過 / 送達 / 已送出)、Phone Number、建立與最後訊息日期、Tags、Intents、訊息內容,還有通話時間長度(部分角色才有)。改完要按 Search。"Show" defaults to "Has Replies": only conversations where the contact has replied are listed. If "a conversation is missing" or the count looks low, switch it to All first. Other filters: Assignee, Link (clicked / delivered / sent), Phone Number, created and last-message dates, tags, intents, message content, and call durations (some roles only). Press Search after changing them.
- 2
標題是「已載入 / 總數 Conversations」,往下捲會繼續載入。🔔 是瀏覽器通知開關,↻ 重新整理清單。每一列顯示聯絡人電話(或姓名、guest)、↩ 表示已經回覆過、@負責人,以及最後一則訊息。The title reads "loaded / total Conversations"; scrolling loads more. 🔔 toggles browser notifications and ↻ refreshes the list. Each row shows the contact's phone (or name, or guest), ↩ if someone replied, the @assignee and the latest message.
- 3
對話上方可以直接把這個聯絡人 Opt-out(已退訂的會顯示 Opted Out,並可以重新加入),☏ 是安排一通電話(Schedule a Call)。Above the chat you can Opt-out this contact directly (opted-out contacts show "Opted Out" with an opt-in button), and ☏ schedules a call.
- 4
目前的負責人。顯示紅色 @None 代表還沒有人負責。The current assignee. A red @None means nobody is assigned yet.
- 5
帳號層會看到所有 Campaign 的對話,所以訊息中間會用橘色分隔線標出「換到哪個 Campaign」。The account level shows every campaign's conversations, so an orange divider marks where the campaign changes within the thread.
- 6
可以直接回訊息(Ctrl + Enter 送出)。聯絡人已退訂時,輸入框會鎖住不能送。You can reply here (Ctrl + Enter sends). The box is locked when the contact has opted out.
- 7
這個聯絡人的歷程時間軸:綠點是對話事件、紅點是排程、藍點是 IVR。有錄音的通話會附播放器。This contact's journey timeline: green dots are conversation events, red are scheduling, blue are IVR. Recorded calls include an audio player.
Campaign 選單裡也有一個 Conversations,那邊只看那一個 Campaign,兩邊數量不同是正常的。The campaign menu has its own Conversations that only shows that one campaign, so different counts are expected.
Users
/usersUser List
1Invite| ID | Name | Invitation Status | System Role 2 | Accounts 3 | Operations | |
|---|---|---|---|---|---|---|
| 32 | Demo Admin | admin@example.test | N/A | System Admin | Acme - Auto Insurance (ID: 101) Account Owner QA Sandbox (ID: 104) Account Admin | EditDeactivate4 |
| 31 | Demo Agent | agent@example.test | Accepted | User | QA Sandbox (ID: 104) Account Agent | EditDeactivate |
| 30 | Demo Analyst | analyst@example.test | Pending | User | Sunrise - Mortgage (ID: 103) Account Analyst | EditRestore |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
Invite 會開「Invite User」視窗:Name、Email、User Role(System Admin / User,預設 User),以及 Accounts —— 從左邊「Available Accounts」把帳號移到右邊「My Accounts」,並替每個帳號選角色。Owner 不能在這裡指定。Invite opens "Invite User": Name, Email, User Role (System Admin / User, default User), and Accounts — move accounts from "Available Accounts" on the left to "My Accounts" on the right and pick a role for each. Owner can't be assigned here.
- 2
System Role 是整個系統的身分:System Admin 看得到帳號選單最下面的 Admin 群組,User 看不到。邀請之後就不能再改。System Role is the system-wide identity: System Admins see the Admin group at the bottom of the account menu, Users don't. It can't be changed after the invite.
- 3
Accounts 列出這個人被加進哪些帳號,以及在每個帳號的角色(彩色標籤)。同一個人在不同帳號可以是不同角色 —— 左側選單看得到哪些項目,是看你在「目前選的那個帳號」裡的角色。Accounts lists which accounts the person belongs to and their role in each (colored tags). One person can hold different roles in different accounts — which left-menu items you see depends on your role in the account currently selected.
- 4
Deactivate 會先確認「Deactivate this user?」;停用的人整列變灰,按鈕變成 Restore 可以恢復。一頁 20 筆。Deactivate asks "Deactivate this user?" first; deactivated users turn gray and the button becomes Restore. 20 per page.
Dashboard(Campaign 層)Dashboard (campaign level)
/▲ 模擬畫面▲ Mock screen
選到 Campaign 之後會回到首頁,但 Campaign 層的首頁目前是空白的 —— 這一頁還沒做,不是載入失敗。要看這個 Campaign 的數字,請到 Stats 底下的 Call Performance Stats。Choosing a campaign takes you back to the home page, but the campaign-level home page is currently blank — it hasn't been built yet; it's not a loading failure. For this campaign's numbers, go to Call Performance Stats under Stats.
沒有 Dashboard 權限的人,在這裡會被自動帶到 Call Performance Stats。People without Dashboard permission are taken to Call Performance Stats automatically.
Settings(帳號層)Settings (account level)
/accounts/{aid}/settingsAccount Settings
Saturday Closed
| ID | Name | Recording Type | Content | Weight | Operations ⓘ |
|---|---|---|---|---|---|
| 12 | After hours EN | Text | We're closed now. Please call again during office hours. | 1 | EditDetach |
No Data, please add at least one voice message setting as default.
No Data, please add at least one voice message setting as default.
| Name | Example | Description |
|---|---|---|
| {{lead_name}} | Tara Priel | Lead's full name |
| {{bot_name}} | My Bot | Agent name / Bot name |
| {{call_time}} | 12:30 PM PST | Call time |
◯ Show Emoji Picker
Characters / Segments …
| ID | Name | Recording Type | Content | Weight | Operations |
|---|---|---|---|---|---|
| 21 | Greeting A | Text | Hi, this is Ava calling about your quote. | 2 | EditDetach |
| 22 | Greeting B | Audio | ▶ ━━━━━━ | 1 | EditDetach |
| API Token | Created At | Operations |
|---|---|---|
| •••••••••••••••• | 09/01/2026 10:00 AM | Delete |
(Token 在手冊裡一律遮起來)(Tokens are always masked in this guide)
| ID | Messaging Service Friendly Name | Messaging Service Sid | Campaign Status | Created At | Operations |
|---|---|---|---|---|---|
| No Data | |||||
| ID | Friendly Name | Status | Trust Bundle Status | Brand Status | Operations |
|---|---|---|---|---|---|
| 3 | Acme Auto | Draft | Create Trust Bundle | Create Brand | Edit and Submit |
▲ 模擬畫面(假資料)。上面的頁籤可以點。▲ Mock screen (sample data). The tabs above are clickable.
- 1
Call Method 是帳號層的轉接連線方式:Dial Transfer 撥給真人號碼,Streaming Transfer 接給 VoiceFusion 或 Vapi 的 AI 助理。點 Dial / Streaming、Phone Number Settings 可以切換看看下面會出現哪些欄位:可以所有 call type 共用一組,或每種分開設。Campaign 沒有自己設時就用這裡的 —— 完整規則見 Transfer(轉接)。Call Method is the account-level transfer connection: Dial Transfer calls a human's number, Streaming Transfer connects to a VoiceFusion or Vapi AI assistant. Click Dial / Streaming and Phone Number Settings to see which fields appear: one set for all call types, or one per type. Campaigns without their own setting use this one — full rules in Transfer.
- 2
Unknown Intent Action:Bot 判斷不出聯絡人在說什麼時怎麼辦(點上面的選單可以切換看看)。Use Default Response = 回覆 Bot 設定裡的「聽不懂」訊息;Assign to Human Agent = 轉給這個帳號的真人 Agent,優先找目前在線、最久沒被分配到的人,帳號沒有 Agent 時改給 Campaign 的管理者。Unknown Intent Action: what happens when the Bot can't tell what the contact means (switch the dropdown above to compare). Use Default Response = reply with the Bot's "unknown" message; Assign to Human Agent = hand it to one of the account's human Agents — preferring whoever is online and least recently assigned, or the campaign manager if the account has no Agents.
- 3
Redirect Domain Name:訊息裡的短網址用哪個網域。Campaign 的 Conversation 頁籤也有 Redirect Domain —— Campaign 有設就用 Campaign 的,沒設才用這裡的。這個欄位要開了功能旗標才會出現。Redirect Domain Name: which domain short links in messages use. The campaign's Conversation tab has a Redirect Domain too — the campaign's wins if set, otherwise this one is used. The field only appears when its feature flag is on.
- 4
Call Recording、Encryption 打開時會先跳出費用確認,因為會增加成本。Turning on Call Recording or Encryption asks you to confirm first, because it adds cost.
- 5
Main 頁籤很長,右側有一排小目錄可以跳到各區。Time 裡的 Office Hour 就是整個帳號的營業時間:打出去的電話只在這個時間撥,打進來的電話在時間外會播 Off Hour 語音後掛斷。The Main tab is long; a small index on the right jumps between sections. Office Hour under Time is the account's business hours: outbound calls are only placed within them, and inbound calls outside them hear the Off Hour message and are hung up.
- 6
改完要按 Submit 才會存;Cancel 會先問「Sure to cancel changes?」再還原。Changes are saved only when you press Submit; Cancel asks "Sure to cancel changes?" before reverting.
- 7
打進來但不在營業時間時播放的語音。三個子頁籤對應 Transfer Mode,系統用的是「Campaign 目前的 Transfer Mode」那一組;有多則時依 Weight 隨機挑一則。至少要留一則,所以只剩一則時不能 Detach。The message played when someone calls outside business hours. The three sub-tabs match the Transfer Modes; the system uses the set for the campaign's current Transfer Mode and picks one at random by Weight. At least one must remain, so the last one can't be detached.
- 8
這張「Transfer Settings」目前不會生效,存得進去但通話時不會讀;實際生效的是 Campaign Settings 的 Transfer 頁籤。This "Transfer Settings" card currently has no effect — it saves, but calls never read it; the Campaign Settings Transfer tab is what counts.
- 9
下半部的語音訊息有效:Campaign 沒有設語音時,會拿這裡同一個 Transfer Mode、同一種 call type 的語音來用。Import 可以用檔案批次匯入。The voice messages below do work: when a campaign has none, the account's messages for the same Transfer Mode and call type are used. Import adds them in bulk from a file.
- 10
美加簡訊合規登記(10DLC)。順序是先建 Business Profile → 建 Trust Bundle、Brand → Brand 通過後才能建 A2P Campaign(在那之前按鈕是灰的)。一個帳號只能有一個 Business Profile。US/Canada SMS compliance registration (10DLC). Order: create the Business Profile → Trust Bundle and Brand → only after the Brand is approved can you create an A2P Campaign (the button stays gray until then). An account can have only one Business Profile.
- 11
Follow up SMS message(未接來電簡訊):預約好時間的外撥電話沒接通(沒人接、忙線或撥打失敗),而且重撥次數已經用完時,自動發這則簡訊給聯絡人。還能重撥的話會先重撥,不會發;電信商直接拒絕撥打的號碼也不會發;不是預約的外撥也不會發。
・Enabled 關著就不發,Template 也不能編輯;打開後 Template 必填。
・Template 可以用三個變數:{{lead_name}}(聯絡人姓名)、{{bot_name}}(Bot 名稱)、{{call_time}}(預約的通話時間)。下方 Preview 會用範例值即時預覽,也會算字數與簡訊則數。
・這是帳號層的設定,帳號底下所有 Campaign 共用;Campaign 那邊沒有自己的一份。
・這一區要開了follow_up_sms_message功能旗標才看得到(旗標還在移除中,見 CT370)。Follow up SMS message (missed-call text): when a scheduled outbound call doesn't connect (no answer, busy or failed) and no redials are left, this text is sent to the contact automatically. If a redial is still allowed, it redials instead; numbers the carrier refuses outright get nothing; outbound calls that weren't scheduled get nothing.
・With Enabled off, nothing is sent and the template is locked; once on, a template is required.
・Three variables are available:{{lead_name}}(contact's name),{{bot_name}}(bot name),{{call_time}}(the scheduled call time). Preview fills in sample values live and shows the character / segment count.
・This is an account-level setting shared by every campaign under the account; campaigns don't have their own copy.
・The section only appears when thefollow_up_sms_messagefeature flag is on (the flag is being removed, see CT370).
這 5 個頁籤只有部分角色看得到。Campaign 也有自己的 Settings,兩邊不一樣。Only some roles can see these 5 tabs. Each campaign has its own Settings too — they're different.
Settings(Campaign 層)Settings (campaign level)
/campaigns/{cid}/settingsCampaign Settings
| Setting Name | Value | Operations |
|---|---|---|
| Conversation Channel | SMS | Edit |
| Redirect Domain | e.g. yourdomain.com | Edit |
| FB Page ID | — | Edit |
| Setting Name | Value | Operations |
|---|---|---|
| Enable Conversation Poke Mechanism | ON | Edit |
| Lead Did Not Reply After X Hours | 24 | Edit |
| Max Repeated Pokes | 2 | Edit |
| Pokes Adhere To Holiday | ON | Edit |
| … Poke Prefix、Poke Response、Do Not Poke If … 等 | ||
| Setting Name | Default Value | Operations |
|---|---|---|
| (列出哪些設定由後端決定)(Which rows appear is decided by the backend) | ||
Choose how the call is connected. The settings here will override the account-level settings.
| Setting Name | Default Value | Operations |
|---|---|---|
| Transfer Mode | Direct Transfer | Edit |
| Pause Seconds Before Transfer | 5 | Edit |
| Transfer Message | Got it, let me connect you now | Edit |
| Answer Machine Detection Status | Off | Edit |
| Target Transfer Phone Number (Deprecated) | — | Edit |
| … Transfer Hours Start / End、Off Working Time Message | ||
No Data, will use account level voice message settings.
| Key Press | Action | Details | Operations |
|---|---|---|---|
| 1 | Transfer | — | Edit |
| 9 | Add to Opt Out List | — | Edit |
SVR 目前沒有客戶使用,暫時棄用。SVR has no customers and is currently deprecated.
| Setting Name | Default Value | Operations |
|---|---|---|
| Appointment Reminder Sms Content | Reminder: we'll call you at your scheduled time. | Edit |
Once enabled, this campaign will send messages using a Short Code and will not be able to receive replies.
▲ 模擬畫面(假資料)。上面的頁籤可以點。▲ Mock screen (sample data). The tabs above are clickable.
- 1
Conversation 頁籤是一張張「設定表」:每列按 Edit 修改,改完按 Save。Conversation Channel(SMS / Web Chat / Facebook / Google Business)在這裡不能改。The Conversation tab is a set of settings tables: press Edit on a row, then Save. Conversation Channel (SMS / Web Chat / Facebook / Google Business) can't be changed here.
- 2
Poke Rules 是「聯絡人沒回覆時要不要再追一則」的規則:幾小時沒回就追、最多追幾次、假日要不要避開、已經排了電話或已經退訂就不追…等。Poke Rules decide whether to follow up when a contact doesn't reply: after how many hours, how many times at most, whether to skip holidays, and not to poke when a call is already scheduled or the contact opted out, and so on.
- 3
Campaign 層的 Call Method 會覆蓋帳號層。這裡沒有「每種 call type 分開設」的選項,一律所有 call type 共用。下面藍色的「Account Level Settings」只是讓你對照帳號層目前設了什麼。The campaign Call Method overrides the account's. There's no "per call type" option here — it always applies to all call types. The blue "Account Level Settings" panel just shows what the account has, for comparison.
- 4
Revert to Account Setting 會刪掉 Campaign 自己的 Call Method、改回用帳號的(會先確認);Campaign 沒有自己的號碼時這顆是灰的。Revert to Account Setting deletes the campaign's own Call Method and falls back to the account's (it asks first); it's gray when the campaign has no number of its own.
- 5
這裡的 Transfer Settings 才是實際生效的:Transfer Mode、停頓秒數、轉接訊息等都看這裡。下面三個子頁籤是各模式的語音訊息;Campaign 沒設時會顯示「No Data, will use account level voice message settings.」,也就是改用帳號層的。These Transfer Settings are the ones that take effect: Transfer Mode, pause seconds, transfer message and so on. The sub-tabs below hold each mode's voice messages; with none set it reads "No Data, will use account level voice message settings." — i.e. the account's are used.
- 6
只有 IVR 子頁籤有 Key Press Action。新建 Campaign 會自動帶「按 1 = Transfer、按 9 = 加入 Opt-out」。表格標示「(Scheduled Call)」,但 Active Dial 與 Inbound 也用同一張。Only the IVR sub-tab has Key Press Action. New campaigns start with "1 = Transfer, 9 = Add to Opt Out List". The table says "(Scheduled Call)", but Active Dial and Inbound use it too.
- 7
打開 Short Code 之後,這個 Campaign 改用短碼發簡訊,但就收不到回覆了。切換時會先確認。With a Short Code on, the campaign sends texts from the short code but can no longer receive replies. Switching asks for confirmation.
- 8
選這個 Campaign 要用哪個 Bot(帳號預設的 Bot 會標「Account Default Bot」)。選了不同的 Bot 之後 Submit 才能按。帳號底下還沒有 Bot 時,會提示你先去建立。Choose which Bot this campaign uses (the account's default is marked "Account Default Bot"). Submit is enabled only after you pick a different Bot. If the account has no Bots yet, it prompts you to create one.
→ 轉接完整說明與流程圖:Transfer(轉接)。→ Full transfer explanation and flow diagrams: Transfer.
Bots
/accounts/{aid}/botsBot List
Chat SimulatorCreate1| Default Bot 2 | ID | Name | Type | Intent Groups | Last Updated At | Reply Mode ⓘ 3 | Operations |
|---|---|---|---|---|---|---|---|
| 7 | Acme Quote Bot | Fusion KB | 3 | 09/20/2026 02:10 PM | Guided | EditDelete4 | |
| 5 | Legacy FAQ Bot | Dialogflow | 0 | 04/02/2026 11:00 AM | N/A | EditDelete |
Create Bot
Set how the bot responds to intents. Applied in priority order: Campaign Intent Level > Account Intent Level > Bot Level.
| 模式Mode | 誰寫回覆Who writes the reply | 跟設定的回覆有多像How close to the configured response | 適合Good for |
|---|---|---|---|
| Fixed | 不經 AI,直接送設定好的文字No AI — the configured text is sent as is | 一字不差Word for word | 法規、價格等不能被改寫的內容;預設值Compliance, pricing and other wording that must not change; the default |
| Guided | AI | 以設定的回覆當範例,AI 被要求「用跟範例相同的風格回答」The configured response is given as an example and the AI is told to "respond in the same style" | 想自然一點、但語氣要一致More natural replies with a consistent tone |
| Flexible | AI | 不給範例,AI 依 Bot、Campaign、聯絡人資料和對話紀錄「自行合適地回答」No example — the AI "responds as appropriate" from the bot, campaign, contact data and chat history | 開放式問答、需要依情境變化Open-ended questions that need context-aware answers |
Scheduling
‹
(選 DialogFlow 時,只剩 Name 和 Type,其他區塊都不會出現)(With DialogFlow, only Name and Type remain; every other section disappears)
▲ 模擬畫面(假資料)。上面可以切換「清單 / 建立 Bot」,建立畫面的 Type 也可以切換。▲ Mock screen (sample data). Switch between the list and Create Bot above; Type is switchable too.
- 1
Chat Simulator 可以直接跟 Bot 對話測試;Create 進入建立 Bot 的畫面。帳號若跟被 fork 的帳號有關、而且對應的功能旗標有開,Create 會鎖住,標題旁會出現橘色提示。Chat Simulator lets you chat with a Bot to test it; Create opens the Create Bot screen. If the account is related to a forked account and the matching feature flag is on, Create is locked and an orange notice appears by the title.
- 2
Default Bot:帳號的預設 Bot,點別的 Bot 的圓點會先確認再換。Campaign 的 Bot 頁籤裡會標示「Account Default Bot」。Default Bot: the account's default; clicking another Bot's radio asks for confirmation before switching. The campaign Bot tab marks it "Account Default Bot".
- 3
Reply Mode 是 Bot 層的回覆模式。實際套用的優先順序:Campaign 的 Intent 設定 > 帳號的 Intent 設定 > Bot 層。FusionKB 呼叫失敗會重試 3 次,還是失敗就退回 Fixed。Reply Mode is the Bot-level reply mode. Priority when applied: campaign intent setting > account intent setting > Bot level. If the FusionKB call fails it retries 3 times, then falls back to Fixed.
- 4
Delete 會連同這個 Bot 的所有 intent、訓練語句、回覆和統計一起刪掉,刪前會確認。點名稱進入 Bot Details(General、Manage Intents、Stats、Training Request 四個頁籤)。Delete also removes all of the Bot's intents, training phrases, responses and stats; it asks first. Click a name for Bot Details (General, Manage Intents, Stats, Training Request tabs).
- 5
Type 決定要填什麼:Fusion KB 要填聽不懂時的回覆、Welcome Message、Reply Mode、Intent Group;DialogFlow 只要 Name。建好之後 Type 就不能改。所有必填都通過前 Create 是灰的。Type decides what you fill in: Fusion KB needs the unknown-intent reply, Welcome Messages, Reply Mode and Intent Groups; DialogFlow needs only a Name. Type can't be changed after creation. Create stays gray until every required field passes.
- 6
For Bot Level:命中 Intent 時用哪種回覆模式,預設 Fixed。三者差異見上方表格。實際套用的優先順序是 Campaign 的 Intent 設定 > 帳號的 Intent 設定 > Bot 層,所以只有 Campaign 和帳號層都沒設時,才會用到這裡。
選 Guided 或 Flexible 時,如果 AI 回了空白或制式的罐頭招呼,系統會改送該 Intent 設定的回覆(跟 Fixed 一樣的文字),避免送出沒內容的訊息。For Bot Level: the reply mode used on a matched intent, default Fixed. See the table above for how the three differ. Priority when applied: campaign intent setting > account intent setting > Bot level, so this is used only when neither the campaign nor the account sets one.
With Guided or Flexible, if the AI returns a blank reply or a generic canned greeting, the system sends the intent's configured response instead (the same text Fixed would), so an empty message never goes out. - 7
Fusion KB 的 Bot 至少要選一個 Intent Group(把左邊的移到右邊)。A Fusion KB Bot needs at least one Intent Group (move from left to right).
- 8
上面這個 Reply Mode 跟下面的 For Bot Level 是兩個不同的設定:這個只管「聽不懂(Unknown Intent)」時怎麼回,下面那個管「命中 Intent」時怎麼回。三個選項的意思相同(見表格),只是範例換成 Unknown Intent Response。這一項只看 Bot 本身的設定,不會被 Campaign 或帳號層覆蓋。預設 Fixed。This Reply Mode and For Bot Level below are two separate settings: this one only covers replies when the bot doesn't understand (Unknown Intent); the one below covers matched intents. The three options mean the same (see the table), with the Unknown Intent Response as the example. This one uses only the Bot's own setting and isn't overridden by the campaign or account. Default Fixed.
這一項只有系統管理員看得到。Only system admins see this item.
Leads
/accounts/{aid}/leadsLead List
| ID | First Name | Last Name | Phone | Zip Code | Created At | Operations 2 | |
|---|---|---|---|---|---|---|---|
| 5021 | Alex | Demo | +15550100001 | alex@example.test | 90001 | 09/30/2026 09:12 AM | DetailsConversations |
| 5020 | Sam | Sample | +15550100002 | — | 73301 | 09/29/2026 04:48 PM | DetailsConversations |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
可以用姓名(不分大小寫)、電話、郵遞區號、建立時間找 Lead。Created At 有 Today / Last 7 days / This Week / This Month 快選。Clear Search 只清空欄位,要再按 Search 才會重查。預設最新的排最上面。Find leads by name (case-insensitive), phone, zip code or creation time; Created At has Today / Last 7 days / This Week / This Month shortcuts. Clear Search only empties the fields — press Search again to re-query. Newest first by default.
- 2
Details 開啟 Lead 基本資料(姓名、Email、電話、郵遞區號、時區、建立 / 更新時間)。資料預設是遮蔽過的,按「Show Unredacted Data」才顯示原始值。Conversations 直接跳到這個 Lead 的對話。Details shows the lead's basic info (name, email, phone, zip, time zone, created / updated times). Values are redacted by default; "Show Unredacted Data" reveals the originals. Conversations jumps to this lead's conversations.
Webhooks
/accounts/{aid}/webhooksWebhook List ⓘ
Create| ID | Endpoint | Http Verb | Created At | Updated At | Operations |
|---|---|---|---|---|---|
| 4 | https://hooks.example.test/ava | POST | 08/01/2026 10:00 AM | 09/10/2026 03:20 PM | EditDelete |
Create a New Webhook
▲ 模擬畫面(假資料)。下半部是按 Create 開出來的視窗。▲ Mock screen (sample data). The lower part is the window Create opens.
- 1
Webhook 會把 Ava 的事件(通話、轉接、Lead、訊息等 23 種)送到你填的 Endpoint。Excluded Events 是「不要送」的清單,不是「要送」的 —— 留空代表全部都送。A webhook sends Ava events (23 kinds: calls, transfers, leads, messages…) to your Endpoint. Excluded Events is a "don't send" list, not a "send" list — leaving it empty sends everything.
- 2
Save 不會先檢查欄位:Endpoint 和 Http Method 雖然標了必填,空著按 Save 一樣會送出。存之前自己確認。Delete 會先問「Sure to Continue?」。Save doesn't check the fields first: Endpoint and Http Method are marked required, but Save submits even if they're empty. Double-check before saving. Delete asks "Sure to Continue?".
跟 Transfer 相關的事件(call_transferring、call_transferred)什麼時候送,見 Transfer(轉接)。For when transfer events (call_transferring, call_transferred) fire, see Transfer.
Speech Synthesis
/accounts/{aid}/voice-messages/speech-synthesisSpeech Synthesis
(跟下面同一張表,一頁 20 筆)(Same table as below, 20 per page)
| Voice | Created Date | Status ⓘ | Text | Audio Preview | Operation |
|---|---|---|---|---|---|
| Rachel | 2026-09-29 | Temporary Expires in 29 Days | Hi, this is Ava… | ▶ ━━━ | Generate URL |
| Rachel | 2026-08-02 | Saved | We're closed now… | ▶ ━━━ | Copy URL |
▲ 模擬畫面(假資料)。頁籤可以點。▲ Mock screen (sample data). Tabs are clickable.
- 1
把文字轉成語音檔(給語音訊息用)。先挑聲音,▶ 可以試聽,標籤是口音、年齡、性別、用途。Turns text into an audio file (for voice messages). Pick a voice first — ▶ previews it; tags show accent, age, gender and use case.
- 2
兩個滑桿預設都是 50%,會記住上次用的值。Both sliders default to 50% and remember your last values.
- 3
一次最多 5000 字。右邊是總額度用量,超過 80% 會變紅。Up to 5000 characters per request. The right side shows total quota used; it turns red above 80%.
- 4
剛產生的錄音是 Temporary,30 天後會過期。要長期使用(例如放進語音訊息)要按 Generate URL 轉成 Saved,之後才能 Copy URL。過期的無法播放。New recordings are Temporary and expire after 30 days. For long-term use (e.g. in a voice message), press Generate URL to make it Saved, then Copy URL. Expired ones can't be played.
左側選單的「Voice Messages」本身沒有頁面,只是 Speech Synthesis 的上層群組。只有系統管理員看得到。"Voice Messages" in the left menu has no page of its own — it's just the parent group of Speech Synthesis. System admins only.
Area Code Coverage
/accounts/{aid}/phone-numbers/area-code-coverage⚠️ 要切到「A2P 設定所在的 Account」才看得到資料。建帳號時如果 Inherit Existed Twilio Account 選了別的 Account(跟著別人的 A2P),這個帳號買的號碼和號碼統計都會記在被繼承的那個 Account 底下,所以在本帳號打開這頁會是空的。請從上方帳號選單切到被繼承的那個 Account 再看,那邊會列出所有共用同一組 A2P 的帳號的號碼。如果這個帳號的 A2P 是自己設定的(建立時沒有選 Inherit),就直接在本帳號看。對照表見 A2P 詳解。⚠️ Switch to the Account that holds the A2P setup to see data here. If the account was created with Inherit Existed Twilio Account set to another Account (sharing its A2P), the numbers it buys and their stats are recorded under the inherited Account, so this page is empty on the current account. Use the account selector to switch to the inherited Account — it lists the numbers of every account sharing that A2P. If this account set up its own A2P (no Inherit at creation), view it right here. See the A2P detail for the mapping.
Area Code Coverage ⓘ
| Area Code ⓘ | Call Count ⓘ | SMS Sent ⓘ | Phone Count ⓘ | Phone Needed ⓘ 3 | Operations |
|---|---|---|---|---|---|
| 213 | 180 | 95 | 1 | 2 | Buy Phone |
| 512 | 60 | 30 | 1 | 0 | Buy Phone |
| 718 | 140 | 20 | 1 | 1 | Buy Phone |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
依區碼比對「通話 / 簡訊量」和「手上有幾支號碼」。選計算基礎(Calls + SMS / Calls / SMS)、日期(預設昨天,不能選今天;昨天的結果 15:30 後才有)、每支號碼的量上限(預設 100),按 View 才會出結果,不會自動載入。Compares call / SMS volume per area code with how many numbers you own. Choose the basis (Calls + SMS / Calls / SMS), a date (default yesterday, today not allowed; yesterday's result is ready after 15:30) and the per-number volume limit (default 100) — results appear only after you press View.
- 2
Buy All 會真的買號碼(會先確認),數量是 Phone Needed 的總和。只有部分角色能按;全部買到或只買到一部分,都會跳出提示。Buy All really purchases numbers (it asks first); the quantity is the sum of Phone Needed. Only some roles can use it; a notice tells you whether all or only some were bought.
- 3
Phone Needed = 為了不超過每支號碼的量上限,這個區碼還要再買幾支。0 的那列 Buy Phone 是灰的。Phone Needed = how many more numbers this area code needs to stay under the per-number limit. Rows with 0 have Buy Phone grayed out.
Number Health Stats
/accounts/{aid}/phone-numbers/stats⚠️ 要切到「A2P 設定所在的 Account」才看得到資料。建帳號時如果 Inherit Existed Twilio Account 選了別的 Account(跟著別人的 A2P),這個帳號買的號碼和號碼統計都會記在被繼承的那個 Account 底下,所以在本帳號打開這頁會是空的。請從上方帳號選單切到被繼承的那個 Account 再看,那邊會列出所有共用同一組 A2P 的帳號的號碼。如果這個帳號的 A2P 是自己設定的(建立時沒有選 Inherit),就直接在本帳號看。對照表見 A2P 詳解。⚠️ Switch to the Account that holds the A2P setup to see data here. If the account was created with Inherit Existed Twilio Account set to another Account (sharing its A2P), the numbers it buys and their stats are recorded under the inherited Account, so this page is empty on the current account. Use the account selector to switch to the inherited Account — it lists the numbers of every account sharing that A2P. If this account set up its own A2P (no Inherit at creation), view it right here. See the A2P detail for the mapping.
Number Health Stats
| Week / Date / Number | Error% | Sent | Errors | A2P Rate 2 | Blocks Rate | Unreachable Rate |
|---|---|---|---|---|---|---|
| ▾ 39(2026-09-21 ~ 2026-09-27) | 1.20 % | 4,210 | 51 | 0.40 % | 0.30 % | 0.50 % |
| +15550100100 | 6.10 % | 820 | 50 | 2.00 % | 1.60 % | 2.50 % |
| Week / Date / Number | Error% | Calls | Errors | Complete | No Answer | Busy | Failed |
|---|---|---|---|---|---|---|---|
| ▾ 39(2026-09-21 ~ 2026-09-27) | 1.00 % | 1,500 | 15 | 1,020 | 400 | 65 | 15 |
▲ 模擬畫面(假資料)。實際是上下兩段(Messages、Calls),這裡做成可切換。▲ Mock screen (sample data). The real page stacks Messages and Calls; here they're switchable.
- 1
每支號碼的「健康度」:簡訊和通話失敗得多不多。上方是共用的報表工具列:選日期區間(沒有預設值)→ 按 🔍;💾 可以把目前的報表存起來,之後從「Select Saved Report」叫出來;⤢ 全螢幕。資料依週 → 日期 → 號碼分層。Per-number health: how often texts and calls fail. The shared report toolbar sits on top: pick a date range (no default) → 🔍; 💾 saves the current report to reopen later from "Select Saved Report"; ⤢ goes full screen. Rows group by week → date → number.
- 2
比率 ≥ 5% 顯示紅色、< 2% 綠色。簡訊錯誤分三類:A2P(電信商每日上限等)、Carrier Violation / Blocks(被電信商擋或過濾)、Unreachable(號碼打不通或是市話)。欄位標題滑過去可以看到對應的錯誤代碼。Rates are red at ≥ 5%, green under 2%. Message errors come in three kinds: A2P (e.g. carrier daily limits), Carrier Violation / Blocks (blocked or filtered by the carrier) and Unreachable (unreachable handset or landline). Hover a header to see the error codes.
Conversion
/accounts/{aid}/stats/conversionConversion
| Week | Total Calls | Total Calls Duration | Inbound Calls | Active Dials | Scheduled Calls |
|---|---|---|---|---|---|
| 39(2026-09-21 ~ 2026-09-27) | … | … | … | … | … |
| Week | Called | Att. Transfers | Att. Transfer% | Transferred | Transferred% | 2Mins+ |
|---|---|---|---|---|---|---|
| 39 | 1,240 | 350 | 28.23 % | 312 | 89.14 % | 140 |
| Week | Received | Att. Transfers | Att. Transfer% | Transferred | Transferred% |
|---|---|---|---|---|---|
| 39 | 210 | 190 | 90.48 % | 180 | 94.74 % |
| Week | Scheduled | Notif Sent | DNC | Called | Called% | Att. Transfers | Transferred |
|---|---|---|---|---|---|---|---|
| 39 | 300 | 290 | 6 | 260 | 86.67 % | 120 | 110 |
| Week | Scheduled | Called | Att. Transfers | Att. Transfer% | Transferred | Transferred% |
|---|---|---|---|---|---|---|
| 39 | 300 | 1,710 | 660 | 38.60 % | 602 | 91.21 % |
▲ 模擬畫面(假資料)。右上的報表選單可以切換。▲ Mock screen (sample data). The report menu at top right is switchable.
- 1
依週統計通話轉接成效。Default Report 顯示所有欄位;選 Active Dials / Inbound Calls / Scheduled Calls / Total Calls 只留那一種通話的欄位。Weekly transfer results by call type. Default Report shows every column; the Active Dials / Inbound / Scheduled / Total presets keep only that call type's columns.
- 2
常見欄位:Att. Transfers 嘗試轉接、Transferred 成功接到轉接號碼、2Mins+ 等是轉接後通話超過 N 分鐘的數量(預設顯示 2/5/10/20/25/30 分鐘,其他長度用 + 加欄位)。轉接相關的百分比 ≥ 90% 綠、< 90% 紅。這些數字怎麼來的,見 Transfer(轉接)。Common columns: Att. Transfers attempted, Transferred reached the transfer number, 2Mins+ etc. count calls lasting over N minutes after the transfer (2/5/10/20/25/30 shown by default; add other lengths with +). Transfer percentages are green at ≥ 90%, red below. Where these numbers come from: Transfer.
Voice Message
/accounts/{aid}/stats/voice-messageVoice Message Stats ⓘ
| Month/Week/Date/Touchpoint Name/Voice Messages | Active/Inactive | Calls | Pick Up % | Att. Transfers | Transfers | 2mins+ % 2 |
|---|---|---|---|---|---|---|
| ▾ 2026-09 | 2,400 | 41.00 % | 380 | 340 | 35.00 % | |
| ▾ 2026-09-21 ~ 2026-09-27 (39) | 620 | 40.30 % | 95 | 86 | 33.70 % | |
| ▾ 2026-09-29 | 90 | 38.90 % | 14 | 12 | 33.33 % | |
| ▾ Active Dial | 620 | 40.30 % | 95 | 86 | 33.70 % | |
| Greeting A(21) | Active | 410 | 42.00 % | 66 | 60 | 36.67 % |
| Greeting B(22) | Inactive | 210 | 37.10 % | 29 | 26 | 11.54 % |
▲ 模擬畫面(假資料)。Month / Week / Day 可以切換。▲ Mock screen (sample data). Month / Week / Day are switchable.
- 1
比較每一則語音訊息(版本)的效果。先選 Call Type(Active Dial / Inbound Call / Scheduled Call)。Month / Week / Day 一次只能勾一個,決定最上層怎麼分,也決定看多久:都不勾與 Month 看近 6 個月、Week 近 3 個月、Day 近 1 個月。Compares each voice message variant. Pick a Call Type first (Active Dial / Inbound Call / Scheduled Call). Only one of Month / Week / Day can be ticked; it sets the top grouping and the time span: none or Month = last 6 months, Week = 3 months, Day = 1 month.
- 2
Active / Inactive 表示這則語音目前有沒有掛在 Campaign 上。百分比 < 15% 紅、≥ 20% 綠。還有一組 SVR 欄位(Responses、Yes),SVR 目前沒有客戶使用。Active / Inactive shows whether the message is currently attached to a campaign. Percentages are red below 15%, green at 20% or more. There's also an SVR column group (Responses, Yes); SVR currently has no customers.
Campaign Performance
/accounts/{aid}/stats/campaign-performanceCampaign Performance
▲ 模擬畫面▲ Mock screen
這頁是把外部報表工具的儀表板嵌進來,版面不在 Ava 程式碼裡,所以這裡沒有辦法模擬內容。報表還沒載入或載入失敗時,卡片是空的。This page embeds a dashboard from an external reporting tool; its layout isn't in Ava's code, so it can't be mocked here. The card is empty until it loads or if loading fails.
Carrier
/accounts/{aid}/stats/carrierBy Carrier
▲ 模擬畫面▲ Mock screen
依電信商看成效的外部報表。每個帳號要另外設定報表來源,沒設定的帳號這頁是空白的。An external dashboard of results by carrier. Each account needs its own report source configured — accounts without one see a blank page.
Line Type
/accounts/{aid}/stats/line-typeBy Line Type
▲ 模擬畫面▲ Mock screen
跟 Carrier 一樣是外部報表,改成依線路類型(手機 / 市話等)分組。沒設定報表來源的帳號這頁是空白的。Like Carrier, an external dashboard, but grouped by line type (mobile / landline, etc.). Blank for accounts without a report source.
Conversations(Campaign 層)Conversations (campaign level)
/campaigns/{cid}/conversationsConversation Filters
20 / 48 Conversations
(555) 010-0001
@Demo AgentTIR2Journey State
▲ 模擬畫面(假資料)。四欄的寬度可以拖曳調整,會記住。▲ Mock screen (sample data). The four columns can be resized, and the widths are remembered.
- 1
跟帳號層的 Conversations 幾乎一樣,但只看這個 Campaign。差別:這裡不會自動選第一則對話、沒有 Campaign 分隔線,而且是即時更新(有新訊息會自動進來)。Show 一樣預設 Has Replies。Almost the same as the account-level Conversations, but only this campaign. Differences: it doesn't auto-select the first conversation, has no campaign dividers, and updates live. "Show" still defaults to Has Replies.
- 2
右上三顆圓鈕是把對話標成 flag_training / flag_intent / flag_review,給訓練或檢查用;已經標過的那顆會變灰。這組只在 Campaign 層有。The three round buttons tag the conversation as flag_training / flag_intent / flag_review for training or review; a button grays out once that tag is on. Campaign level only.
- 3
這裡的 Export 下載的檔名是「Intents Trainings 日期.xlsx」,內容是對話資料,不要被檔名誤導。Export here downloads a file named "Intents Trainings <date>.xlsx" — it contains conversation data despite the name.
Tags
/campaigns/{cid}/conversations/tagsTags ⓘ
CreateRefresh| Tag Name | Type 1 | Conversations | Messages | Created by | Created at | Operations 2 |
|---|---|---|---|---|---|---|
| Interested | Custom | 34 | 51 | Demo Agent | 08/12/2026 10:00 AM | EditDelete |
| answer_machine_detected | System | 12 | 0 | — | 02/14/2026 09:00 AM | EditDelete |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
這個 Campaign 的對話 / 訊息標籤,以及各被用了幾次。System 是系統自動建的,Custom 是人建的。Create 只要輸入名稱。This campaign's conversation / message tags and how often each is used. System tags are created automatically, Custom ones by people. Create only asks for a name.
- 2
名稱可以直接在表格裡改(Edit → Save)。System 標籤不能改也不能刪。Rename right in the table (Edit → Save). System tags can't be edited or deleted.
Intent Actions
/campaigns/{cid}/ai/intents-actionsIntent Actions ⓘ
Create| User Intents / Actions | Operations |
|---|---|
| ▾ Wants a call | |
| Call Now | EditDelete |
| ▾ Stop | |
| Add to Optout List | EditDelete |
Create New Action
▲ 模擬畫面(假資料)。Action 可以切換。▲ Mock screen (sample data). Action is switchable.
- 1
偵測到某個 intent 時自動執行的動作。Call Now 要填延遲秒數;Schedule Time To Call 不用填;Add To Optout List(也有 Global / Organization / Account 範圍的版本)要選退訂原因(Opt Out / Profanity / Stop / Wrong Number)。建好後 Intent 和 Action 都不能改,只能刪掉重建。An action that runs automatically when an intent is detected. Call Now needs a delay in seconds; Schedule Time To Call needs nothing; Add To Optout List (also Global / Organization / Account versions) needs a reason (Opt Out / Profanity / Stop / Wrong Number). After creation Intent and Action can't be changed — delete and recreate instead.
- 2
名稱陷阱:「Transfer to Campaign」是把 Lead 移到另一個 Campaign 的流程,不是電話轉接。只能選其他啟用中的 Campaign。Naming trap: "Transfer to Campaign" moves the lead into another campaign's flow — it is not a phone transfer. Only other enabled campaigns are listed.
Intent Tree
/campaigns/{cid}/ai/intents-treeIntents Tree ⓘ
Show DetailsExpand All1▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
把 intent 之間怎麼接續(例如 Welcome 之後接 Welcome - Yes)畫成由左到右的圖。一開始只顯示最上層的 intent,可以一層層展開;頁首的 Expand All 會一次載入全部。右下角可以縮放。Draws how intents follow each other (e.g. Welcome → Welcome - Yes) left to right. Only top-level intents show at first and expand level by level; the header's Expand All loads everything. Zoom from the corner controls.
- 2
每個節點按 Load Details 才會顯示訓練語句(前 5 句)與回覆;頁首的 Show Details 一次載入所有看得到的節點。Each node shows its training phrases (first 5) and responses only after Load Details; the header's Show Details loads every visible node at once.
Manage Intents
/campaigns/{cid}/ai/intentsManage Intents
| Intent | Response | Response Created At | Reply Mode ⓘ | Custom Response |
|---|---|---|---|---|
| Wants a call Campaign | Great! When is a good time? | 09/10/2026 | Guided | EditDelete |
| Office hours Default | We're open 9–5. | — | Fixed | CreateDelete |
Manage Intents
Create IntentDFFrom DFTo DF2Copy From CampaignImport Intent Groups| User Intent / Response Message |
|---|
| ▸ Welcome WelcomeEnabled EditAdd follow-up intent ▾Delete |
▲ 模擬畫面(假資料)。依 Bot 類型是兩種不同的畫面,可以切換。▲ Mock screen (sample data). There are two different screens depending on the Bot type — switchable.
- 1
Fusion KB:列出這個 Campaign 會用到的 intent 與回覆,標籤顯示回覆是哪一層定義的(Default / Account / Campaign)。可以替某個 intent 建「這個 Campaign 專用」的回覆;刪掉就退回上一層。Default 和 Account 層的不能在這裡刪。Fusion KB: lists the intents and responses this campaign uses; the tag shows which level defines the response (Default / Account / Campaign). You can create a campaign-only response for an intent; deleting it falls back to the level above. Default and Account ones can't be deleted here.
- 2
Dialogflow:左邊是 intent 清單(可以展開看訓練語句與回覆、加 follow-up intent),右邊可以直接測試對話。From DF / To DF 按下去就會在背景同步,不會再確認;同步進行中其他按鈕都會鎖住。帳號跟被 fork 的帳號有關時,這頁也可能被鎖住。Dialogflow: the intent list on the left (expand for training phrases and responses, add follow-up intents), a test chat on the right. From DF / To DF start a background sync immediately, with no confirmation; other buttons lock while it runs. The page can also be locked when the account is related to a forked account.
Code Snippet
/campaigns/{cid}/web-chat/code-snippetWeb Chat Code Snippet Generation ⓘ
/* web chat 內嵌程式碼 */
</script> 1
▲ 模擬畫面(程式碼內容以示意取代)▲ Mock screen (code replaced with a placeholder)
- 1
產生要貼到客戶網站上的 Web Chat 內嵌程式碼。左邊改設定,右邊的程式碼會自動更新,點一下就複製。範本帳號不能用這個功能。Generates the Web Chat embed code for a customer's website. Change settings on the left and the code on the right updates; click it to copy. Not available for template accounts.
- 2
Send Test Message 會開新視窗跑這段程式碼,並真的送一則測試訊息到對話裡給負責的 Agent。Send Test Message opens a new window running the code and really sends a test message into a conversation for the agent.
Settings(Web Chat)Settings (Web Chat)
/campaigns/{cid}/web-chat/settingsWeb Chat Settings ⓘ
▲ 模擬畫面(假資料)。頁籤和 Office Hours 的三個選項可以點。▲ Mock screen (sample data). Tabs and the three Office Hours options are clickable.
- 1
網站聊天視窗的營業時間(預設開在這個頁籤)。24/7、Mon-Fri 會直接填好並鎖住每天的時段,選 Custom 才能自己調。這是 Web Chat 自己的時段,跟帳號 Settings 的 Office Hour 是分開的。Business hours for the website chat (the default tab). 24/7 and Mon-Fri fill in and lock each day; choose Custom to edit. These are Web Chat's own hours, separate from the account Settings Office Hour.
- 2
Submit 只會存「目前這個頁籤」,切到別的頁籤改完要再按一次。Auto Popup 的欄位留空代表關閉。Submit saves only the current tab — press it again after changing another tab. Leaving an Auto Popup field blank disables it.
Custom Posts
/campaigns/{cid}/webhooksCustom Posts ⓘ
Create| ID | Type | Name | Endpoint | HTTP Method | Operations |
|---|---|---|---|---|---|
| 9 | Call Transferred | CRM - transferred | https://crm.example.test/hook | POST | EditDelete |
Create Custom Post
▲ 模擬畫面(假資料)。下半部是按 Create 開出來的視窗。▲ Mock screen (sample data). The lower part is the window Create opens.
- 1
Campaign 層的「事件發生時,把資料送到客戶的網址」。跟帳號層的 Webhooks 不同:這裡每一筆只針對一種事件(Type),而且可以自己決定送哪些欄位。Type 建好後就不能改。偵測到 intent 這類的 Type 會多一個 Meta 區塊,可以選要哪些 intent(或 ALL)。Campaign-level "send data to the customer's URL when something happens". Unlike account Webhooks, each one targets a single event Type and you choose which fields to send. Type can't be changed after creation. Intent-detected types add a Meta section to pick intents (or ALL).
- 2
Payload 分 Dynamic(Key 對到系統欄位)和 Static(固定值),只支援一層的 JSON。Payload has Dynamic rows (key mapped to a system field) and Static rows (fixed values); only one-level JSON is supported.
- 3
Test 會用範例資料實際打一次 Endpoint,並顯示回應。Test 一律用 POST 送,不管上面選的是哪個 HTTP Method。Test really calls the Endpoint once with sample data and shows the response. Test always sends POST, whatever HTTP Method is selected above.
轉接相關的 Custom Post(Call Transferring / Call Transferred / Call End)什麼時候送,見 Transfer(轉接)。For when transfer-related Custom Posts fire (Call Transferring / Call Transferred / Call End), see Transfer.
Call Performance Stats
/campaigns/{cid}/conversations/call-performance-statsCall Performance Stats
| Week | Convo Created | Wlc Msg Sent | Resps | Stop Msgs | Schedules Made | Link Clicked | CTR% |
|---|---|---|---|---|---|---|---|
| 39 | 1,200 | 1,150 | 310 | 22 | 95 | 140 | 31.20 % |
| Week | Scheduled | Notif Sent | DNC | Att. Transfers | Transferred | 2Mins+ |
|---|---|---|---|---|---|---|
| Week | Called | Att. Transfers | Att. Transfer% | Transferred | 2Mins+ | |
| Week | Received | Att. Transfers | Att. Transfer% | Transferred | 2Mins+ | |
| Week | Scheduled | Notif Sent | DNC | Called | Called% | Transferred |
| 39 | … | … | … | … | … | … |
▲ 模擬畫面(假資料)。Call Type 可以切換。▲ Mock screen (sample data). Call Type is switchable.
- 1
上半部是簡訊到排程的漏斗:建立對話 → 歡迎訊息送出 → 有回覆 → 排到電話;以及連結的送出、送達、點擊。百分比 ≥ 30% 綠、< 10% 紅。沒有權限看 Dashboard 的人會被帶到這一頁。The top half is the SMS-to-schedule funnel: conversations created → welcome sent → replies → calls scheduled, plus links sent, delivered and clicked. Percentages are green at ≥ 30%, red below 10%. People without Dashboard permission land on this page.
- 2
下半部是通話與轉接,依週分組。Call Type 會換欄位:Inbound 看 Received(打進來的),Active Dials 看 Called(撥出去的),Scheduled 還有排程、通知、DNC。The bottom half is calls and transfers by week. Call Type swaps the columns: Inbound shows Received, Active Dials shows Called, Scheduled adds scheduling, notifications and DNC.
- 3
Call Duration(部分角色才有):Transfer Duration = 從轉接成功開始算的時長;Full Duration = 整通電話的時長。時長怎麼算見 Transfer(轉接)。Call Duration (some roles only): Transfer Duration counts from a successful transfer; Full Duration counts the whole call. How durations are computed: Transfer.
Conversion Stats
/campaigns/{cid}/conversations/conversion-statsConversion Stats
| Week / Date | Total Calls | Connected | Connected% | Conversions 1 | Cvr Value | Cvr% | Hangup% |
|---|---|---|---|---|---|---|---|
| 39 | 820 | 690 | 84.15 % | 41 | $2,050 | 5.00 % | 22.00 % |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
Connected = 接到轉接號碼的通話;Conversions / Cvr Value = 轉換數與轉換金額;Hangup = 聯絡人自己掛掉(Missed Call)。Connected% ≥ 80% 綠。Connected = calls that reached the transfer number; Conversions / Cvr Value = conversion count and value; Hangup = the lead hung up (missed call). Connected% is green at ≥ 80%.
Voice Message Stats
/campaigns/{cid}/ivr/greeting-messages/statsVoice Message Stats ⓘ
| Month/Week/Date/Voice Messages | Calls | Pick Up % | Responses | Yes | Att. Transfers | Transfers |
|---|---|---|---|---|---|---|
| Greeting A(21) | 410 | 42.00 % | 120 | 44 | 66 | 60 |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
跟帳號層的 Voice Message 類似,但只看這個 Campaign,沒有日期篩選;Group By 預設 month / week / day 全勾,可以一層層展開。只有「SVR Mode」一個頁籤,而 SVR 目前沒有客戶使用。Similar to the account-level Voice Message but for this campaign only, and with no date filter; Group By has month / week / day all ticked by default. There's just one tab, "SVR Mode" — and SVR currently has no customers.
Intent Response Stats
/campaigns/{cid}/ai/intents-responses/statsIntent Response Stats ⓘ
| User Intent/Week/Date | Sent # | User Response % | Intent Known % | Schedule % | Stop % |
|---|---|---|---|---|---|
| ▾ Welcome (ID: 11) | 1,150 | 27.00 % | 81.00 % | 8.30 % | 1.90 % |
| ▾ 2026-09▾ 2026-09-21 ~ 2026-09-27▾ 2026-09-29 | … | … | … | … | … |
| Hi! This is Ava from Acme… | 600 | 29.00 % | 83.00 % | 9.10 % | 1.50 % |
▲ 模擬畫面(假資料)。Monthly / Weekly / Daily 可以切換。▲ Mock screen (sample data). Monthly / Weekly / Daily are switchable.
- 1
每個 intent 的每一種回覆(Ava 說的話)效果如何:送出幾次、聯絡人回了多少、回的內容 Ava 聽不聽得懂、有多少接著排了電話、多少回了 stop。依 intent → 月 / 週 / 日 → 回覆內容分層,預設 Monthly;從 Monthly / Weekly 切換時會清掉日期篩選。How each response (what Ava says) of each intent performs: times sent, how many leads replied, whether Ava understood the reply, how many went on to schedule a call, and how many said stop. Grouped intent → month / week / day → response, default Monthly; switching intervals clears the date filter.
Link tracking Stats
/campaigns/{cid}/conversations/link-trackingLink Tracking Stats
| Date | Links Sent | Clicks | CTR% | Conversion 1 |
|---|---|---|---|---|
| 2026-09-29 | 320 | 41 | 12.81 % | 3 |
| 2026-09-28 | 298 | 35 | 11.74 % | 2 |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
訊息裡連結的成效,一天一列、最新的在上面,沒有分組。How links in messages perform — one row per day, newest first, no grouping.
Web Chat Stats
/campaigns/{cid}/web-chat/statsWeb Chat Stats
| Week | Impressions | Sessions | Unique Responses | Leads | Total Calls | Transfers |
|---|---|---|---|---|---|---|
| 39 | 5,400 | 610 | 220 | 95 | 60 | 41 |
▲ 模擬畫面(假資料)。可以切換 Campaign 的頻道看差別。▲ Mock screen (sample data). Switch the campaign's channel to compare.
- 1
網站聊天的漏斗:頁面載入(Impressions)→ 開始聊天(Sessions)→ 有回覆 → 建成 Lead → 通話與轉接。Campaign 的對話頻道不是 Web Chat 時,這頁只會顯示一行「不是 Web Chat」的提示,不是壞掉。The website chat funnel: page loads (Impressions) → chats started (Sessions) → replies → leads → calls and transfers. If the campaign's channel isn't Web Chat, the page shows just a "not Web Chat" line — that's expected.
Contexts
/contextsContexts
| Applied To | Context 1 | Last Updated At | Operations |
|---|---|---|---|
| Acme (ID: 3) | Acme sells auto and home insurance in CA and TX… | 09/02/2026 10:00 AM | EditDelete |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
替組織、帳號、Campaign 或 Bot 附上一段文字說明(Context)。四個頁籤各管一種;建立時先選套用對象(Campaign / Bot 要先選帳號再選),建好後套用對象不能改。Attach a free-text Context to an organization, account, campaign or Bot. Each of the four tabs handles one kind; when creating, pick what it applies to (for campaigns / Bots pick the account first). The target can't be changed afterwards.
Organizations
/organizationsOrganizations
Create| ID | Name | Description | Accounts | Operations |
|---|---|---|---|---|
| 3 | Acme | Insurance group | 2 | EditDelete |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
組織是帳號的上一層。建立時可以綁一個 Short Code(要先在 Short Codes 新增)、把帳號移進來;已經屬於別的組織的帳號不能選,而且建好之後帳號清單就不能在這裡改。編輯時會顯示這個 Short Code 目前被幾個啟用中的 Campaign 使用。An organization sits above accounts. When creating one you can link a Short Code (add it in Short Codes first) and move accounts in; accounts already in another organization can't be picked, and the account list can't be changed here after creation. Editing shows how many active campaigns use the Short Code.
Accounts
/accountsAccount List
Create1| ID | Name | Created At | Updated At | Operations | Business Hours 3 |
|---|---|---|---|---|---|
| 101 | Acme - Auto Insurance | 02/01/2026 | 09/20/2026 | EditDelete | ON |
Create New Account
▲ 模擬畫面(假資料)。下半部是按 Create 開出來的視窗。▲ Mock screen (sample data). The lower part is the window Create opens.
- 1
要先把自己的帳號連結 Google 登入,Create 才按得了,不然滑過去會提示「Please link to google first.」。帳號在這裡不能刪(Delete 永遠是灰的)。Create only works after you link your login to Google; otherwise hovering says "Please link to google first.". Accounts can't be deleted here (Delete is always gray).
- 2
填的轉接號碼會同時存成帳號層的 Call Method(Dial Transfer、所有 call type 共用),所以新帳號一建好就有轉接設定。要改用 Streaming 請到帳號 Settings。Inherit Existed Twilio Account 只有部分人看得到:沿用別的帳號的 Twilio,不另外建立。The transfer number is saved as the account-level Call Method too (Dial Transfer, shared by all call types), so a new account has a transfer setup right away. Switch to Streaming in the account Settings. Inherit Existed Twilio Account (visible to some only) reuses another account's Twilio instead of creating a new one.
- 3
Business Hours 是整個帳號的營業開關,切換會立刻存:關掉 = 把每一天的 Office Hour 都設成關閉(原本的時段會先備份),等於帳號停止撥號、打進來只會聽到 Off Hour 語音;再打開 = 還原備份的時段。只要有任何一天是營業就顯示開。Business Hours is the whole account's open/closed switch and saves immediately: turning it off closes every day's Office Hour (backing up the current hours first) — the account stops dialing and inbound callers only hear the Off Hour message; turning it back on restores the backed-up hours. It shows on if any day is open.
Internal Performance Stats
/accounts/internal-performance-statsInternal Performance Stats
| Date | Leads Posted | Active Leads | Engaged % | Total Optout % | Total Transferred | Revenue | Total Cost | Gross Margin % 2 |
|---|---|---|---|---|---|---|---|---|
| 2026-09-29 | 1,000 | 820 | 31.00 % | 4.20 % | 60 | $1,800 | $640 | 64.44 % |
Conversion Definitions 3
Pricing: 50
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
- 1
公司內部看的營運與損益。先選一個組織或其中一個帳號,沒選之前下面的表格不會出現;選單一帳號時會顯示它的收費模式。Internal performance and profit. Pick an organization or one of its accounts first — the table doesn't appear until you do; for a single account its payment model is shown.
- 2
欄位分四組:Lead(送進來幾筆、有互動的、退訂)、通話(轉接數)、連結(送出、送達、點擊)、營收與成本(Revenue、成本、毛利、毛利率;毛利是負的會變紅)。日期可以依月 / 週 / 日分組,預設 Daily。Four column groups: leads (posted, active, engaged, opted out), calls (transfers), links (sent, delivered, clicked), and revenue & cost (revenue, cost, gross profit and margin; negative profit turns red). Dates group monthly / weekly / daily, default Daily.
- 3
每個 Campaign、每一天的「怎樣算一次轉換、一次值多少」:點日期上的 ✎ 設定 Pricing 和 Unit(Lead / Call Conversion / Sale);選 Call Conversion 還要設轉接時長超過幾秒才算。Per campaign and per day, "what counts as a conversion and what it's worth": click ✎ on a date to set Pricing and Unit (Lead / Call Conversion / Sale); Call Conversion also needs a minimum transfer duration.
Intent Knowledge Base
/intent-knowledge-baseIntent Knowledge Base
| ID | Name | Intents 1 | Last Updated At | Operations |
|---|---|---|---|---|
| 2 | Insurance FAQ | 14 | 09/01/2026 | EditDelete |
| ID | Display Name | Description | Action 2 | Last Updated At | Operations |
|---|---|---|---|---|---|
| 31 | Wants a call | Lead asks to be called | ✓ | 09/01/2026 | EditDelete |
| ID | Name | Description | Type 3 | Last Updated At | Operations |
|---|---|---|---|---|---|
| 1 | callback_time | When the lead wants a call | Date & Time | 08/20/2026 | EditDelete |
▲ 模擬畫面(假資料)。頁籤可以點。▲ Mock screen (sample data). Tabs are clickable.
- 1
Fusion KB Bot 用的 intent 資料庫。Intent Group 是一組 intent,建 Fusion KB Bot 時要選(見 Bots);每組至少要有一個 intent。The intent library used by Fusion KB Bots. An Intent Group is a set of intents chosen when creating a Fusion KB Bot (see Bots); each group needs at least one intent.
- 2
Intents:每個 intent 的名稱與描述;綠色 ✓ 表示有綁動作(Call Now、Schedule time to call、Add to Optout List、Transition to Different Campaign)。Intents: each intent's name and description; a green ✓ means it has an action (Call Now, Schedule time to call, Add to Optout List, Transition to Different Campaign).
- 3
Named Entities:要從對話裡抓出來的資料(目前只有 Date & Time 一種),描述會告訴 AI 怎麼用它。Named Entities: data to extract from conversations (currently only Date & Time); the description tells the AI how to use it.
Holiday Settings
/holiday-settingsHoliday Setting
Create| ID | Name | From | To | Operations |
|---|---|---|---|---|
| 5 | Thanksgiving | 2026-11-26 00:00 | 2026-11-27 23:59 | EditDelete |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
設定假日時段,並選要套用到哪些帳號。時段是依帳號設定裡的時區計算。假日期間系統不會排電話(排程時會回覆「因假日無法接聽」),Poke 規則也可以設定避開假日。Define holiday windows and choose which accounts they apply to. Times follow the time zone set in account Settings. During a holiday calls aren't scheduled (the lead is told the office is closed for the holiday), and Poke rules can be set to skip holidays.
API Keys
/api-keysAPI Keys
Create| ID | Name | API Key | Organization Name | Accounts | Last Updated At | Operations |
|---|---|---|---|---|---|---|
| 2 | Acme integration | Copy | Acme | 2 | 09/01/2026 | EditDelete |
▲ 模擬畫面(假資料)▲ Mock screen (sample data)
組織層級的 API Key(跟帳號 Settings 裡的 API 頁籤不同)。表格上不顯示金鑰本身,只能按 Copy 複製。建立時要選組織,之後組織就不能改。Organization-level API keys (different from the API tab in account Settings). The key itself isn't shown — only Copy. You pick the organization when creating, and it can't be changed later.
Short Codes
/short-codesShort Codes ⓘ
Search Short Code+ Add| Name | Code | Used By | Provisioned Date | Operations |
|---|---|---|---|---|
| Acme reminders | 55501 | Acme | 06/01/2026 09:00 AM | EditDelete |
Add Short Code
▲ 模擬畫面(假資料,憑證欄位一律遮起來)▲ Mock screen (sample data; credential fields always masked)
Short Code 是 5 或 6 位數、可大量發送的簡訊號碼。在這裡新增後,才能到 Organizations 綁到組織,再到 Campaign Settings 的 SMS 頁籤打開(開了之後那個 Campaign 就收不到回覆)。號碼和憑證建好後都不能改。A Short Code is a 5- or 6-digit high-volume SMS number. Add it here, then link it to an organization in Organizations, then switch it on in the campaign Settings SMS tab (after which that campaign can't receive replies). The number and credentials can't be changed after creation.
(這一項的介紹整理中)(This item's explanation is being written.)
🔒 = 不是所有帳號角色都看得到這一項。選單結構整理自 ava-client 2026-09-08 版。🔒 = not every account role can see this item. Menu structure taken from ava-client as of 2026-09-08.
登入 / 註冊 / 忘記密碼Sign in / Sign up / Forgot password
登入前的三個頁面不在左側選單裡。點「詳解」看每一頁的欄位、按鈕與注意事項。The three pages before sign-in aren't in the left menu. Open "Detail" for each page's fields, buttons and gotchas.