Contact
Talk to a person. Not a form.
Every route below reaches the same inbox and a human replies. Pick whichever describes you, and the subject line will already say what it is about.
A question
Anything about the product, security, deployment or the training. If it turns out to be a common one, it ends up on the FAQ.
Team access
Per-seat access for a department or a whole organization, with single sign-on and the governance dashboard. Tell us roughly how many seats and we will come back with a number.
Enterprise and deployment
Private cloud, an isolated tenant or an on-premise install, with the security review that goes with it. This is the route if procurement is involved.
Just want to use it
Individual access is self-serve. Open the app, and the apps for iPhone and Android are in the stores.
What to put in the first message
None of this is required, and there is no form here that will ask you for it. It is simply what turns a first reply into an answer rather than a request for more detail, and it is the same handful of things almost every conversation needs before it can get anywhere useful.
- Roughly how many people
- A department of thirty and an organization of three thousand are different conversations. One is a per-seat question; the other usually starts with where the deployment lives. An approximate number is enough to know which one we are having.
- Where the data has to stay
- If a classification, a regulator or an internal policy already rules out a shared environment, say so at the start. It decides which of the three deployment shapes is even on the table, and it is the single thing most likely to make the rest of the conversation moot.
- What people will actually do with it
- Drafting, questions across your own documents, analysis, teaching, or a mix. The workspace is the same either way. The training we point you at, and the examples worth showing you, are not.
- Whether procurement is involved
- A security review, a vendor questionnaire or a formal tender changes the sequence rather than the answer. Knowing it is coming means the documentation arrives with the first reply instead of three emails later.
- What you are using today
- Licences bought by one team, a pilot that stalled, or nothing sanctioned at all. Where you are starting from shapes the first month more than anything else on this list, and shadow use is a starting point like any other.
What happens next
A person reads the message and replies. Depending on what you asked, that reply is the answer itself, the document your review needs, or a time to talk. There is no qualification call standing between you and a real conversation, and nothing here starts a sequence of automated follow-ups.
Where we are
AI Plus Labs is incorporated in Singapore and the team works in Singapore time, which is worth knowing if you are writing from Europe or the Americas. Where the platform itself runs is a separate question with a different answer: it is deployed into the cloud account, tenant or data centre you nominate, so the region your data sits in is decided by your own infrastructure rather than by ours.
The address
Everything above is a pre-filled email to this address, so writing directly works just as well.
AI PLUS LABS PTE LTD, Singapore.
However you arrive, the message lands in the same place and a person reads it. No queue, no ticket number, no bot asking you to rephrase.