Tickets by Category
Tickets by Priority
Recent Tickets
| # | Subject | Client | Category | Priority | Status | Date |
|---|
No pending approvals
Time Entries by Incident
No time entries yet. Click Add Time Entry to start tracking.
Monthly Ticket Volume
Status Distribution
Tickets by Client
Ticket Summary by Category
| Category | Total | Open | In Progress | Resolved | Closed |
|---|
All Tickets (Individual)
| # | Subject | Company | Category | Priority | Status | Consultant Assigned | Created |
|---|
Root Cause Analyses
| # | Subject | Root Cause | Preventive Action | Completed |
|---|
Timesheet Report
Showing 0 entries, 0 total hours. Leave dates blank to include everything.
| Date | Consultant | Ticket | Activity | Hours | Billable |
|---|
Supabase Connection
App URL (for email links)
If this app is only opened as a local file (file:///C:/...), links inside outgoing emails — like "Verify My Email" or "View Ticket" — will point to that local file path and won't work for anyone else. Once you host this app somewhere with a real web address (Netlify, Vercel, your own server, etc.), paste that address here so email links work properly for everyone.
Email Service (Resend)
Get your key from resend.com/api-keys
Masase Help Desk
Supabase Project
Admin Account
SQL Setup
Run this in Supabase SQL Editor to create the tickets and agents tables:
id uuid primary key default gen_random_uuid(),
ticket_number serial,
first_name text not null,
last_name text not null,
email text not null,
phone text, company text,
category text not null,
priority text default 'Medium',
subject text not null,
description text not null,
status text default 'Open',
assigned_agent_id uuid,
sla_policy text,
created_at timestamptz default now(),
updated_at timestamptz default now()
);
alter table tickets enable row level security;
create policy "Allow all" on tickets
for all using (true) with check (true);
-- Add missing columns if table already exists
alter table tickets add column if not exists email text;
alter table tickets add column if not exists phone text;
alter table tickets add column if not exists company text;
alter table tickets add column if not exists assigned_agent_id uuid;
alter table tickets add column if not exists sla_policy text;
-- RPC function (bypasses schema cache issues)
create or replace function create_ticket(
p_first_name text, p_last_name text, p_email text,
p_phone text default null, p_company text default null,
p_category text default 'General Inquiry',
p_priority text default 'Medium',
p_subject text default '', p_description text default '',
p_assigned_agent_id uuid default null,
p_sla_policy text default null
) returns json language plpgsql security definer as $$
declare v_id uuid; v_num int;
begin
insert into tickets(first_name,last_name,email,phone,company,
category,priority,subject,description,status,
assigned_agent_id,sla_policy)
values(p_first_name,p_last_name,p_email,p_phone,p_company,
p_category,p_priority,p_subject,p_description,'Open',
p_assigned_agent_id,p_sla_policy)
returning id,ticket_number into v_id,v_num;
return json_build_object('id',v_id,'ticket_number',v_num);
end; $$;
create table if not exists agents (
id uuid primary key default gen_random_uuid(),
first_name text not null, last_name text not null,
email text not null unique, phone text,
role text default 'Agent', department text,
status text default 'Active',
password_hint text, notes text,
created_at timestamptz default now(),
updated_at timestamptz default now()
);
alter table agents enable row level security;
create policy "Allow all" on agents
for all using (true) with check (true);
notify pgrst, 'reload schema';
Email Notifications (Supabase)
✅ System: Supabase Email Service (Active)
✅ New User Email: Enabled
✅ Ticket Assignment Email: Enabled
✅ SLA Breach Email (3-Strike): Enabled
Sent when a new user account is created. Includes login credentials and link.
Sent when a ticket is assigned to an agent. Includes ticket details and priority.
Strike 1: Warning to agent
Strike 2: Urgent alert to agent
Strike 3: Critical escalation to agent + managers
✅ Supabase email service is configured and ready to use.
✅ All 3 Edge Functions deployed and active.
✅ Emails will be sent automatically for all events above.
No additional setup required!
SLA Policies
| Policy Name | Priority | Response Time | Resolution Time | Escalation After | Business Hours | Status |
|---|
SLA Ticket Report
Connect Supabase to load ticket SLA data
Active SLA Breaches
No active SLA breaches
Connect Supabase to load agents
Account Details
How it works
1. Fill in the form
Enter all required details for the new account.
2. Account created
Account is created and stored in Supabase.
3. Verification email
A confirmation email is sent to the new user.
4. User activation
User verifies email and account is fully activated.
Password Requirements:
• At least 8 characters
• Mix of uppercase & lowercase
• At least one number
All Clients
No clients yet. Click Add Client to create one.
Tickets by Type
Add ticket types to see breakdown
Your Tickets
No tickets yet. Submit your first ticket below!
Submit New Ticket
Tell us about your issueUser Profile
Change Password
Workspace
Profile Display
Email Notifications (Supabase)
✅ System: Supabase Email Service (Active)
✅ New User Email: Enabled
✅ Ticket Assignment Email: Enabled
✅ SLA Breach Email (3-Strike): Enabled
📧 Email Provider: Supabase built-in service
Automatically sent when a new user account is created. Includes email, role, and temporary password.
Automatically sent when a ticket is assigned to an agent. Includes ticket #, subject, client, and priority.
• Strike 2: Urgent alert to agent
• Strike 3: Critical escalation to agent + all managers
✅ Supabase email service is fully configured and ready.
✅ All 3 Edge Functions are deployed and active.
✅ Emails will be sent automatically for all events above.
✅ No EmailJS configuration needed.
No FAQs yet. Add your first FAQ to help customers.