Do I need a developer to connect another system?

For WhatsApp Business through Meta's official API, SkyInbox or Chatwoot, Front, GitHub, Shopify, n8n, Make and Zapier, the setup comes pre-filled and the connection test confirms it. For an in-house system, IT points the event delivery to the integration address and chooses what each event does on the board.

Which plan do I need?

Inbound integrations, calls to an integration and the API require a plan with API access. The month's electronic signatures follow the plan quota.

Can AI answer the customer on its own?

Only if the board owner turns on, in the rule, the option to send AI text without a person's review. Without that release, the message coming from AI does not go out, and the release is dropped when the rule changes owner.

Is the signature legally valid?

Skyller keeps the document sent, the signed document, the signature sheet and the request trail, with date, IP and device, and location only with the signer's consent. Whether this kind of signature works for a specific contract is a question for your legal team.

Can the board be taken to another environment?

The portability package carries the board structure, records, integrations and prompts in one file, with a preview of what changes before saving. Cards and secrets stay out of the package.

Kanban · Integrations

Requests come in wherever they arrive. And the board answers.

Forms, the board inbox, WhatsApp and other systems open the card; rules and AI executors move the phase forward; and the board notifies other systems, generates the document and requests the signature.

Try it free Book a demo

See how it works

Skyller · Service desk

Service desk

Inputs

Board

#318 · came in through WhatsApp BusinessCopy of the invoice

NewIn progressWaiting for customerResolved

Entry rule: assign through the rotation. Phase AI: fill in the Subject.

Outputs

Answer on the channel
Signed notice to other systems
Document and signature, when the rule asks

Demonstration · illustrative data

6 WAYS IN

form, board inbox, integration, API, spreadsheet and AI assistants

16 TRIGGERS · 23 ACTIONS

up to 10 actions per rule, with conditions and waits

SIGNATURE ON THE CARD

the PDF goes to up to 10 signers and comes back with the request trail

SIGNED NOTIFICATIONS

each event goes to other systems in the open Standard Webhooks format

Where this shows up in your day

The request came in five ways. Nobody knows which one is late.

Customer service

The customer wrote on WhatsApp, by email and through the website form

Each channel has its own inbox, and the same request shows up three times or not at all. Nobody can say how many requests came in yesterday or who has each one.

One board for every input

Contracts

The approved contract that went back to email

After the board says yes, someone downloads the template, fills it in by hand, exports a PDF and sends it for signature elsewhere. The card sits in Approved.

Document and signature on the card

IT and operations

The system that only finds out at month end

The ERP needs to know when the order was completed, and today that depends on someone copying the number into another screen.

The other system notified on the event

How it works

In, through and out, with rules at every step.

01
The request comes in
Through the form (with a public link, a password or company-only), the board inbox, an integration with another system, the API or a spreadsheet read every hour. Each input becomes a card in the first phase.
02
The phase has rules
Required fields per phase, who can move cards, owners on entry and deadlines per phase and for the whole process, in calendar or business days. Every phase change goes through the same gate, which checks all of that.
03
Automation does the work
Rules with 16 triggers and 23 actions: move, fill in, notify, send email, create a subcard, generate a document, request a signature, call an integration or wait. The Simulate tab shows what would happen, without saving anything.
04
AI does its part
A Skyller agent, team or workflow works on the phase: it reads the card, fills in and suggests fields, comments and requests validation. A tool that needs approval waits for whoever configured the AI to decide.
05
The board answers
The message goes back to the customer through the integration channel, email goes out from the board address and other systems receive the signed event. Text written by AI only goes out with the board owner's release, rule by rule.

Live proof

One request on WhatsApp, three phases, the answer on the same channel.

Starting point
The Service desk receives the company's WhatsApp Business messages through an integration, on a board that runs from New to Closed, through In progress, Waiting for customer and Resolved.
What happens
1. 01The customer asks for a copy of her invoice. The integration creates the card in New with name, phone and message, and the conversation stays on the card itself.
2. 02The entry rule assigns the card through the team rotation, and the phase's AI executor reads the request, sets the Subject to Invoice, receipt or billing and comments a proposed answer.
3. 03The agent reviews it, writes the answer on the card and sends it to the customer. The message goes out on WhatsApp, and the card shows Sent, Delivered and Read.
Result
The request had an owner, a deadline and a history from start to finish, and the customer got the answer on the channel she wrote on.

Skyller · Card #318 · history

Card #318 · history

Service desk · ResolvedCopy of the invoiceSubject: Invoice, receipt or billing · Owner: Ana

Card created with name, phone and message09:12 · origin: WhatsApp Business integration
Assigned to Ana through the rotation09:12 · origin: board automation
Subject filled in and proposed answer commented09:13 · origin: phase AI
Answer sent to the customer on WhatsApp · Sending09:20 · origin: Ana
“Card moved” event delivered to the finance system, signed09:20 · Standard Webhooks format

Demonstration · illustrative data

Good to know

The integration receives events in the open Standard Webhooks format. WhatsApp Business (Meta's official API), Shopify, GitHub and n8n come in through shortcuts that fill in that setup, not through a ready-made connector for each one.
AI answering the customer directly only happens if the board owner releases it, rule by rule. Without that, text coming from AI waits for a person.
Integrations and the API require a plan with API access. The live spreadsheet only reads: it creates and updates cards, but does not write to the sheet.

Company, customer and people are fictional; the phases, the integration and the message states are the product's.

To evaluate calmly

How work comes in, what runs inside and what goes out.

Select a topic to see its capabilities, conditions, and limits.

Forms and portal: An intake form for anyone with the link, for the whole company or for chosen people, with a password, verification and embedding on your website. The portal releases each record with an expiry and authorized people.
Board inbox: Each board gets an address, and each card its own address. The email becomes a card, lines in the Label: value format fill in fields without AI, and senders can be filtered by domain or members only.
Inbound integration: Another system notifies Skyller, and the card is created, changes phase, gets a comment, an attachment or a delivery status, according to the mapping. An unverified event is held until a person decides.
API and live spreadsheet: The API creates, reads, updates, moves and comments on cards with a key of chosen reach. The Google or Excel Online spreadsheet is read on demand, every hour or every day, and updates items by key.

Frequently asked questions

What people ask before connecting the first channel.

Start with the messiest input

Connect the channel where most requests arrive.

Open the Service desk from the template, connect the board inbox or WhatsApp Business and watch each request become a card with an owner and a deadline.