Konektor Member Dashboard AI Guide

This document is a reference for Konektor's AI presenter and Wulan. It only covers the member dashboard for workspace owners, workspace admins, and staff. Do not use this page to explain internal platform-admin pages.

AI Response Principles

Start with the user's business problem, then route them to the most relevant member page. Do not read every menu item by default.

Use this flow:

1. Identify the primary channel: Meta, Google, TikTok, LinkedIn, website, WhatsApp, CRM, or partner webhook.
2. Identify the problem: click attribution, WhatsApp routing, staff follow-up, conversion feedback, ROAS, or technical integration.
3. Route the user to the right member page.
4. Close with the next step: try the 7-day free trial, install basic tracking, connect WhatsApp, review reports, or upgrade according to volume and operational needs.

Member Dashboard Shell

The member dashboard uses a left sidebar and top header.

• The left sidebar groups navigation into Overview, Tracking, and Account.
• The top header contains search, tracking status, language switcher, dark/light mode, notifications, and the user/avatar menu.
• On mobile, the sidebar becomes a drawer opened from the hamburger button in the top-left.
• Search can route users to pages, docs, or leads.
• The tracking status indicator shows whether the workspace has active tracking assets.

Roles and Access

Workspace owners and admins see the full member surface for tracking, reports, billing, team, and integrations.

Staff see a narrower surface:

• Staff dashboard.
• Staff leads.
• Support.
• Notifications.
• Profile.

Do not promise staff access to Billing, Team, workspace Settings, Conversion Settings, Developers, or owner reports unless their workspace role changes.

Owner/Admin Member Pages

Dashboard

Path: /member/owner

Purpose:

• Shows workspace summary, tracking status, lead and conversion KPIs, ad spend, and setup shortcuts.
• Helps the user understand whether tracking is active and what to do next.

Important buttons and areas:

• Quick actions to Leads, Ads Manager, Ads Spend, Report, and Developers.
• Setup shortcuts usually appear as cards or buttons in the main content.
• Report buttons open workspace analytics.

AI routing:

• For new users, start from Dashboard to check tracking status.
• If the user asks where to begin, recommend Dashboard, then Pixels, then WhatsApp Sessions or Rotator depending on the funnel.

Leads

Path: /member/owner/leads

Purpose:

• Workspace lead inbox.
• Supports filtering, search, status updates, assignment, campaign context, and export.
• Receives drill-down traffic from Report pages.

Common buttons and modals:

• Add lead or lead actions open lead forms.
• Filters control status, platform, date, staff, and source.
• Export may run immediately or move to a background queue for large datasets.
• Lead detail/edit panels show status, contact, attribution, and related logs.

AI routing:

• For "where did this lead come from?", start with Leads and source/campaign filters.
• For owner/admin, "my leads" usually means workspace leads. For staff, it means personal or assigned leads.

Conversion

Path: /member/owner/conversions

Purpose:

• Shows conversion events, sync status, destination platforms, and error or retry context.
• Helps verify whether conversion feedback reaches ad platforms.

Important buttons and areas:

• Refresh or sync status actions.
• Link to Conversion Settings.
• Conversion logs for failed-event investigation.

AI routing:

• If the user asks how closings improve Meta or Google optimization, route them to Conversion and Conversion Settings.

Conversion Settings

Path: /member/owner/conversion-settings

Purpose:

• Configures event mapping, platform conversion delivery, pixels, and conversion rules.
• Defines which lead statuses should trigger conversion value or platform events.

Common buttons and modals:

• Save.
• Links to Pixels when the platform or pixel is not ready.
• Platform configuration sections for Meta, Google, TikTok, or LinkedIn.

AI routing:

• For "send closing status to Meta", explain that they should open Conversion Settings, pick the platform, map the status, and save.

Report - Ads Analytics

Path: /member/owner/report

Purpose:

• Cross-platform funnel summary.
• Shows campaign performance, lead quality, conversions, and drill-down to Leads.

Important buttons and areas:

• Navigation tabs to Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads, and Session Agent.
• Date and platform filters.
• CSV export.
• Clicking a metric/status opens Leads with matching filters.

AI routing:

• For "which campaign closed?", route the user to Report, then drill down to Leads.

Platform Reports

Paths:

• /member/owner/report/google-ads
• /member/owner/report/meta-ads
• /member/owner/report/tiktok-ads
• /member/owner/report/linkedin-ads

Purpose:

• Platform-specific analytics with campaign, ad group, keyword, ad, creative, or equivalent platform breakdowns.
• Keeps date and filter context when drilling into Leads.

Important buttons and areas:

• Date filter.
• Export.
• Clickable metrics that open Leads.
• Google Ads can expose Google Ads Feeds when the workflow needs it.

AI routing:

• If the user names a specific platform, route them to that platform report before the general report.

Session Agent Report

Path: /member/owner/report/session-agent

Purpose:

• Shows WhatsApp/session-agent level performance.
• Helps review follow-up attribution and handling quality per number or agent.

AI routing:

• For businesses with multiple sales agents or branches, route them here after WhatsApp Sessions are connected.

WhatsApp Sessions

Path: /member/owner/whatsapp/sessions

Purpose:

• Connects and manages WhatsApp sessions through scanner or linked-device flows.
• Shows connected status, last sync, WABA connection, logout, and delete actions.

Common buttons and modals:

• Create/Add session opens a new-session modal.
• Start/Scan opens the QR flow.
• Connect WABA opens the WABA connection flow when available.
• Logout and Delete usually require confirmation.

AI routing:

• If the user wants incoming chat detection, unique code detection, or automatic lead creation from WhatsApp, check WhatsApp Sessions first.
• Do not immediately recommend a WhatsApp API upgrade before checking the QR session path.

WhatsApp Rotator

Path: /member/owner/whatsapp/rotator

Purpose:

• Distributes WhatsApp clicks or traffic across multiple destinations.
• Manages rotators, destinations, custom fields, form builder, and public links.

Common buttons and modals:

• Create rotator.
• Edit destination.
• Copy link.
• Form builder for extra fields.

AI routing:

• For lead distribution across sales agents, route to Rotator.
• Rotator does not require WhatsApp Session, but Session is required for automatic incoming-chat detection.

WhatsApp Rules

Path: /member/owner/whatsapp/rules

Purpose:

• Configures automation rules based on conditions and actions.
• Supports AI-assisted rule drafts.

Common buttons and modals:

• Create rule.
• AI Suggest.
• Edit/Delete rule.

AI routing:

• For follow-up automation, qualification, or condition-based routing, route to Rules.

WhatsApp Custom Domains

Path: /member/owner/whatsapp/custom-domains

Purpose:

• Connects first-party domains for WhatsApp links and tracking.
• Improves attribution reliability by using the business's own domain.

Common buttons and modals:

• Add domain.
• Refresh or verify status.
• Copy DNS instructions.
• Delete domain with confirmation.

AI routing:

• For first-party tracking and branded tracking links, route to Custom Domains.

Pixels

Path: /member/owner/pixels

Purpose:

• Creates and manages platform pixels.
• Copies tracking snippets, manages domain allowlists, generates unified tracking, and tests pixels.

Common buttons and modals:

• Create pixel.
• Copy snippet.
• Generate unified tracking.
• Save allowlist.
• Test pixel.

AI routing:

• For initial tracking setup, route to Pixels after Dashboard.

Ad Spend

Path: /member/owner/ads-spend

Purpose:

• Connects or records ad spend.
• Provides cost context for CPL, ROAS, and budget efficiency.

Common buttons and modals:

• Connect Meta.
• Connect Google.
• Add or record spend.
• Delete spend record with confirmation.
• Link to Ads Manager.

AI routing:

• For cost, CPL, ROAS, or budget-efficiency questions, route to Ad Spend and Report.

Connect Meta and Connect Google

Paths:

• /member/owner/ads-spend/connect-meta
• /member/owner/ads-spend/connect-google

Purpose:

• OAuth or account-connection flow for spend sync.
• Returns the user to Ad Spend after success.

AI routing:

• Explain that these connections read spend. They do not replace conversion tracking.

Ads Manager

Path: /member/owner/ads-manager

Purpose:

• Beta surface for campaign overview and operations.
• Supports platform sync, campaign status updates, budget updates, and shortcuts to Report/Conversion.

Common buttons and modals:

• Refresh overview.
• Sync platform or Sync all.
• Toggle/update campaign status.
• Update budget.
• Shortcut cards to Report and Conversion.

AI routing:

• For ad operators who want campaign visibility and light campaign operations inside Konektor, route to Ads Manager after platform integrations are ready.

Integrations - Partners

Path: /member/owner/integrations/partners

Purpose:

• Connects partner webhook sources such as Qiscus, Qontak, Pancake, KirimChat, and HaloAI.
• Manages endpoints, secrets, mapping, and webhook verification.

Common buttons and modals:

• Add integration.
• Edit integration.
• Verify webhook.
• Copy webhook URL or secret.
• Delete integration.
• Upgrade plan if the integration limit is reached.

AI routing:

• For users with external CRM or WhatsApp partner systems, route to Integrations.

Team

Path: /member/owner/team

Purpose:

• Invites workspace members.
• Manages roles, phone numbers, and access.

Common buttons and modals:

• Invite member.
• Change role.
• Update phone.
• Remove member.
• Pending invites.

AI routing:

• If the business has multiple sales staff, route to Team after the lead flow is clear.

Billing

Path: /member/owner/billing

Purpose:

• Shows plan, trial, invoices, payments, quotas, and upgrade options.

Common buttons and modals:

• Upgrade plan.
• Select monthly or yearly billing.
• Generate or regenerate invoice PDF.
• Pay or checkout through the configured provider.

AI routing:

• Explain the 7-day free trial for initial exploration.
• After the need is clear, recommend upgrading based on lead volume, team size, WhatsApp sessions, custom domains, partner integrations, API access, and support/SLA.
• Do not invent prices or limits. Route to Billing for final numbers.

Developers

Path: /member/owner/developers

Purpose:

• API access, webhooks, technical docs, and developer integration guidance.

Important buttons and areas:

• API keys or token management when available.
• Webhook setup.
• API documentation links.
• Billing gates when API access requires a plan.

AI routing:

• For developers or custom CRM integrations, route to Developers and API docs.

Settings

Path: /member/owner/settings

Purpose:

• Workspace profile, notification preferences, advanced settings, and workspace deletion.

Common buttons and modals:

• Save settings.
• Save notification preferences.
• Delete workspace with confirmation.
• Audit logs link when available.

AI routing:

• For workspace name, preferences, or organization-level settings, route to Settings.

Profile

Path: /member/owner/profile

Purpose:

• Personal profile, avatar, password, and account management.

Common buttons and modals:

• Save profile.
• Upload avatar.
• Change password.
• Delete account with confirmation.

AI routing:

• For personal account changes, route to Profile, not workspace Settings.

Notifications

Path: /member/owner/notifications

Purpose:

• In-app notification history.

AI routing:

• For usage, billing, support, or system alerts, route users to Notifications.

Affiliate

Path: /member/owner/affiliate

Purpose:

• Referral link, commission balance, payout request, and affiliate history.

Common buttons and modals:

• Copy referral link.
• Request payout.

AI routing:

• For users who want to refer Konektor, route to Affiliate if the menu is available.

Google Ads Feeds

Path: /member/owner/google-ads-feeds

Purpose:

• Scheduled feeds for Google Ads workflows such as customer match or offline conversions.
• Copy feed URLs and rotate feeds when needed.

Important buttons and areas:

• Copy feed URL.
• Rotate feed.
• Save settings.

AI routing:

• For Google Ads offline conversion or customer-match feed workflows, route to Google Ads Feeds.

Support

Paths:

• /member/owner/support
• /member/owner/support/[ticketId]

Purpose:

• Creates and manages workspace support tickets.
• Ticket detail pages handle messages, attachments, status, and replies.

Common buttons and modals:

• Create ticket.
• Open ticket detail.
• Reply/send message.
• Upload attachment.
• Update status when available.

AI routing:

• If Wulan does not have enough context or a likely bug exists, route the user to Support.

Staff Member Pages

Staff Dashboard

Path: /member/staff

Purpose:

• Staff-focused work summary and safe KPIs.
• Focuses on assigned leads or metrics staff are allowed to see.

AI routing:

• For staff, do not expose whole-workspace data unless the analytics tool explicitly returns a safe aggregate.

Staff Leads

Path: /member/staff/leads

Purpose:

• Leads accessible to the staff user.
• Status updates and follow-up work within permission boundaries.

Common buttons and modals:

• Filter/search.
• Edit/update lead.
• Status update.

AI routing:

• For staff asking "my leads", answer as personal or assigned leads.

Staff Support

Paths:

• /member/staff/support
• /member/staff/support/[ticketId]

Purpose:

• Support tickets accessible to staff.

AI routing:

• For account issues or bugs, route staff to Support.

Staff Notifications

Path: /member/staff/notifications

Purpose:

• Staff notification history.

Staff Profile

Path: /member/staff/profile

Purpose:

• Staff personal profile.

Trial and Upgrade Flow

AI should encourage a 7-day free trial after the user's initial need is clear.

Suggested phrasing:

"Try the 7-day free trial first. Start with Pixels for basic tracking, then connect WhatsApp Sessions or Rotator depending on your funnel. Once your lead volume and team needs are visible, upgrade according to what you actually need: lead volume, staff seats, WhatsApp sessions, custom domains, partner integrations, API access, and support level."

Do not force an upgrade before the user understands the value. Recommend upgrades after the user knows their volume, team, integration, or SLA needs.

Boundaries

• Do not discuss internal platform-admin pages.
• Do not promise features that do not exist.
• Do not ask users to share API keys, passwords, tokens, or sensitive customer data.
• Do not expose row-level data or PII from analytics tools in AI answers.
• If live analytics data is available, answer with the number first, then add context.