ChatGPT Plugin

Krewss BI

Hotel operations insights

Brand: Krewss

Category: Data & Analytics
Primary Subcategory: Self-Serve BI & Conversational Analytics

Integration details

Description

Krewss BI answers management questions from the operational data hotel teams already capture in Krewss: how yesterday went, which incidents repeat and in which rooms, who is on duty now, which guest requests were served late and what was asked for, which returning guests are in-house with their stay history, and how the property's Google rating is trending. Every figure drills down to the tasks, SOP submissions or guest requests behind it and links back to the record in Krewss. It is read-only and scoped to the signed-in user's organisation: users sign in with their Krewss credentials and only accounts granted Krewss BI access can connect.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Data & Analytics
Primary Subcategory: Self-Serve BI & Conversational Analytics
Secondary Subcategories: None listed
Brand: Krewss
Access: Account required
First tracked: 2026-09-25
Tool count: 14
Market: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT Self-Serve BI & Conversational Analytics

View Category

Listed in alphabetical order

Primary Subcategory

ADECIComing soonGet notified

Adzviser Google AnalyticsComing soonGet notified

Adzviser ShopifyComing soonGet notified

AI for DatabaseComing soonGet notified

AI2SQLComing soonGet notified

Krewss BIComing soonGet notified

Tools

14 tools agents can invoke

The individual records behind a number — each row carries name, deliverables (what was asked for, e.g. Water Bottle, Towel), area/asset, guest, crew, status, scheduled/SLA, timings and last note. subject = tasks or sops. kind examples — tasks: all, completed, onTime, late, open, pending, overdue, escalated, incidents, guest, status, group, priority, type, area, name, deliverable, guestName; sops: all, completed, open, abandoned, flagged, status, group, area, name. value is the bucket for status/group/priority/type/area/name.
Fetch one record by id (task ids look like 2026-08-25-0001, SOP submission ids likewise). Returns the full record as text.
Google rating, review count, star split, rating trend and the latest reviews for a site (only when the Google Reviews add-on is enabled).
get_google_reviews
Guest requests for a site and period (KPIs, per day/hour, by department, top requests/deliverables/rooms, repeat requests) plus the repeat guests currently in-house with their visit history summary and requests in the period.
get_guest_voice
Crew right now: headcount, by department, and who is clocked in (name, department, designation, since when).
get_members_live
Headline totals for tasks and SOP submissions in a period: total, completed, late, open, overdue, escalated, completion/on-time rates. Org-wide or one site.
get_overview
A returning guest's full stay history (every stay with room and dates) and the requests raised in each stay. Identify by name or mobile.
get_repeat_guest_history
One SOP submission in full: checkpoints with answers and flags, activity trail, timings.
get_sop_submission
SOP compliance for a site and period: submissions, completed, open, abandoned, flagged, by group, top SOPs, top flagged, top abandoned, repeat flags.
get_sops_summary
One task in full: details, assignees, timings, deliverables and the progress-note trail. Use the id from a drilldown or search.
get_task
Task analytics for a site and period: KPIs, by group / priority / type, top requests, top incidents, top maintenance, and repeat incidents (same area + same issue 2+ times). Honours the area scope.
get_tasks_summary
List the properties (sites) of this organisation with their ids. Call this first to get a siteId.
list_sites
Task history analytics (from 2026-07-01 onward, refreshed hourly). PREFER THIS over get_tasks_summary/drilldown for ANY question about patterns over time, at any date range, including ranges under 3 months. It is the ONLY tool that can answer: which areas/rooms/assets have REPEATED problems (minCount), and WHEN each was LAST reported (last_seen) and FIRST reported (first_seen). get_tasks_summary/drilldown cannot count recurrence or return a last-reported date, and cap at 92 days. Trigger words: regularly, repeatedly, recurring, again, keeps happening, frequent, repeat offenders, chronic, over the last N months, since <month>, trend, history, when was it last. For complaints/problems/faults filter taskType:"incident" (taskType:"service" is routine requested work like amenities and cleaning, which will otherwise dominate the counts). IMPORTANT - many task names are CONTAINERS and the real request is in the DELIVERABLE: "Housekeeping Amenities" alone covers 52 different items (Water Bottle, Towel, Dental Kit, Slippers...). So whenever the question is about WHAT guests or staff asked for, or about a named item, add "deliverable" to groupBy (e.g. groupBy ["area","deliverable"]) or filter deliverable:"Towel" - grouping by task alone will report one meaningless row. Deliverable groups count items, not tasks, and exclude tasks that name no item. Omit groupBy to list individual task records; set groupBy to aggregate. Example — "rooms with issues regularly since August, and when it last happened": start "2026-08-01", groupBy ["area","task"], filters {taskType:"incident"}, minCount 3 -> read last_seen for the most recent date. Add stillOpen true for "still unresolved". For repeat-guest questions group by guest_id: it is an OPAQUE hashed key (never a phone number or email) that still groups the same guest exactly across stays, and each row carries a readable `guest` name to quote in the answer - report the name, never the guest_id itself. Phone/email are only recorded for tasks raised from 2026-10-17 onward, so for earlier periods group by guest instead and say that repeat counts are name-matched and may merge namesakes.
query_task_history
Search tasks and SOP submissions by text (task/SOP name, guest name, area, group) in a period. Returns ids for fetch.

FAQs

Krewss BI ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve Krewss BI's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Krewss BI alternatives on ChatGPT?

As of 2026-11-02, Krewss BI competes with ADECI, Adzviser Google Analytics, Adzviser Shopify, AI for Database, AI2SQL, Alteryx Insights, AnalyticsLog, Anomaly AI and 81 more in ChatGPT Self-Serve BI & Conversational Analytics, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.