Skip to main content
The Plural support team is here to help you get the most out of your Avatar, Pepper, Temi, or NAO deployment. Reach out through any of the channels below and the team will get back to you as quickly as possible.

Support Channels

Send your question or issue to:support@humanizing.comEmail is the best channel for detailed technical questions, sharing screenshots, or following up on an existing ticket. Include your ticket number in the subject line when replying to an open case.
Call the Plural support team directly:+49 173 43 43 000Phone support is available during service hours (see below). Use this channel for urgent issues or when you need to talk through a problem in real time.
Submit a support request online at:plural.io/support-for-plural-and-digital-service-staffThe contact form is useful if you are not sure which team to route your request to, or if you want to attach files alongside your description.

Support Hours

The Plural support team is available:
DayHours (CET)
Monday – Friday09:00 – 17:00
Saturday – SundayNot available (see note below)
Public holidaysNot available (see note below)
Weekend and public-holiday support can be arranged on request with a minimum of 2 weeks’ notice. Additional charges apply. Contact support@humanizing.com to arrange this.
Self-Help resources — including the documentation, Knowledge Base, and weekly webinar recordings — are available 24/7.

Writing a Good Support Ticket

The more detail you provide upfront, the faster the team can help you. Include all of the following in every ticket:
1

Describe the problem clearly

State exactly what is happening and what you expected to happen instead. Use plain language — you do not need to diagnose the root cause.
2

List all steps that led to the issue

Reproduce the problem in your head and write down every step, starting from opening Plural or powering on the robot. This helps the team reproduce the issue on their end.
3

Include your project name

Specify the name of the Plural project you were working in or that the robot was running at the time. If the issue is not project-specific, note that instead.
4

Include your account email address

Provide the email address associated with your Plural account so the team can look up your setup quickly.
5

Attach screenshots or photos

A screenshot of an error message or a photo of the robot’s display is worth a thousand words. Attach as many visuals as are helpful.
If your issue involves a Pepper robot and you need to escalate to the manufacturer, also gather Pepper’s Body ID (found inside the neck flap) and software version before you write. See Robot FAQ for details.

Advanced Webinars

If you want to deepen your Plural skills or get hands-on guidance for a specific feature, you can book a dedicated advanced webinar with the Humanizing team: Book an advanced webinar Weekly beginner and advanced webinars are also available as part of the Self-Help support tier — check the Plural documentation for the current schedule and recordings of past sessions.