We're on the HiBob Marketplace now. If you run HR in Bob and your company lives in Slack, this one's for you.
Suptask is the help desk that sits inside Slack, so employees ask for things where they already are and HR and IT get them as tickets. Hook it up to Bob and three things change:
- the requester's details land on the ticket the moment it arrives
- agents can check and change Bob data without opening another tab
- Suptask AI takes the routine questions (vacation days left, mostly) off your plate
Fewer trips to Bob, quicker answers, and your team only touches the requests that actually need a person.
Every change in HiBob creates work somewhere else
Anna gets added to Bob on a Tuesday. She starts the Monday after. Somewhere between those two dates IT needs to order a laptop and create her accounts, HR needs the contract signed and a first week put together, and Finance wants her in payroll before the cutoff. None of them know yet, because the only system that does is Bob.
That's most internal requests, really. Someone joins, switches teams, gets a new manager, goes on leave or hands in their notice, and a little trail of tickets follows. Usually it starts as a DM to whoever in IT happens to be online. Then that person opens Bob, finds the record, copies the department and start date into the ticket by hand, and only then gets going on the actual work.
HR already lives in Bob. Everyone else lives in Slack. Suptask sits in Slack and can now read from Bob and write back to it, so the people data stays where it is and the requests stay where they are.
What the integration does
It goes both ways. Bob can open a ticket in Slack, and a Suptask AI Assistant can look things up in Bob, or change them, from inside that ticket.
Bob opens the ticket
This is the bit people tend to miss. When Bob posts into a Slack channel, say a new hire starting Monday, Suptask picks the message up and turns it into a ticket on whichever Inbox you point it at. Nobody has to remember to raise it. If you control what Bob writes you can drop field markers into the message, and the ticket shows up with priority and tags already filled in.
Suptask reads from Bob
This is the everyday part. When a ticket comes in, Suptask matches the requester to their Bob profile by email and adds department, manager and job title to the ticket. From there the Assistant on that Inbox can:
- search employees and read their fields
- pull up departments and sites
- check time off balances
- see who's out today or next week
- read someone's onboarding or offboarding task list
Suptask writes back, with a person in between
Given the permissions, the Assistant will create an employee record, update fields on an existing one, or submit a time off request on someone's behalf. Each change is shown to an agent first. They approve it on the ticket, it's saved in Bob, and the approval stays on the ticket so you can see who said yes and when.
Put together, this is what happens as someone moves through the company:
The onboarding ticket that Bob kicks off is one ticket. It goes from HR to IT to Finance with one owner at a time, and anyone can see where it's sitting. We've found that works a lot better than a parent ticket with six children nobody closes.
What it looks like day to day
Onboarding
The one most customers set up first is onboarding. HR adds the new hire in Bob and has Bob post to a channel, we usually suggest something like #hibob-events. Suptask turns that post into a ticket on the IT Inbox. The Assistant reads Anna's department, manager and start date from Bob and puts them on the ticket, and IT can order the laptop and request access without asking HR a single question. When IT is done the ticket moves on to Finance for payroll. HR watches the whole thing from Slack and never has to chase.
The HR inbox
Then there's the HR inbox itself. "How many days do I have left?" and "who's out next week?" are probably the two most common questions HR gets, and neither needs a human. Set the read tools to Auto and the Assistant answers them on the ticket straight from the requester's own Bob record. You decide which questions it's allowed to handle alone. What's left for the HR team is the stuff that genuinely needs them.
Changes to Bob
Changes are the part people are nervous about, so here's how that goes. A manager raises a ticket to move someone to a new team, or an employee asks to book a week off. The Assistant prepares the change in Bob, stops, and shows it to an agent on the ticket. One click and it's saved. The agent hasn't left Slack, and Bob hasn't had an edit nobody looked at.
Tools are set per Assistant, so your HR Assistant can create and update employees while the IT one on another Inbox just reads. Finance, Facilities and Ops get the same context on their tickets, which in our experience is all they wanted anyway.
How it works
You'll need a service user in Bob and a few minutes. No developer required.
- In HiBob, create an API service user under Settings → Integrations and copy its Service User ID and Token.
- Put the service user in a dedicated permission group, for example "Suptask AI integration", and assign only the categories you want Suptask to reach.
- In Suptask, open Intelligence, pick the Inbox, add the HiBob connector and paste the two values.
- Set each tool to Off, Ask or Auto for the Assistants that should use it.
The service user isn't tied to a person, so the connection keeps working after whoever set it up has left. And the permission group in Bob is the hard limit. Suptask can't read or change anything that group doesn't allow, which makes it easy to start narrow and widen later when you trust it.
Our usual advice:
- read tools on Auto
- write tools on Ask
- everything you don't need on Off
The full walkthrough, the tool list and the troubleshooting bits are in the HiBob integration guide. The connector is part of AI workflows on the Custom Enterprise plan.
The ticket should start where the change happens
People data changes in Bob. Requests get worked in Slack. For years the thing connecting those two has been someone copying details from one into the other and hoping the right team spotted it.
Now the change in Bob can be what opens the ticket, the ticket carries the right context from the start, and the answer can go back into Bob without anyone switching tabs. That's the whole idea.
Already on Bob and Slack? Find Suptask on the HiBob Marketplace, follow the integration guide, or book a demo and we'll set up the onboarding flow with you.
