Skip to main content
This guide walks you through everything you need to get up and running on WeCareRemote — from creating your account to sending your first message to the AI assistant. The whole process takes just a few minutes.

​
Before you begin

You will need:
  • An email address that can receive verification messages
  • A modern browser (Chrome, Firefox, Safari, or Edge) with cookies enabled
  • An internet connection
  • For video calls: a working microphone (camera optional)
If you are joining on behalf of an NGO, your organization should provision your account with the org_admin role before you sign up. Refugee users are typically assigned the blog role on first registration.
1

Visit the platform and sign up

Go to wcr.is/home and click Sign Up to create a new account. If you already have an account, click Log In and enter your credentials.
WeCareRemote handles authentication automatically when you log in through the platform. Your session is secured with a JWT token, so you stay logged in across the AI assistant, blog, and video features without any extra steps.
2

Choose your role

When you register, your account is assigned a role that determines what you can access:
  • Refugee user (blog role) — You can chat with the AI assistant and read content on the blog. This role is designed for refugees seeking information and support from NGOs.
  • NGO administrator (org_admin role) — You can do everything a refugee user can, plus manage and publish blog content and access administrative features for your organization.
If you are unsure which role applies to you, contact your NGO directly. Role assignment is managed by your organization’s administrator.
3

Open the AI assistant

After logging in, navigate to the AI Assistant from the main navigation. The chat interface loads your conversation history automatically, so any previous sessions are available when you return.
4

Send your first message

Type your question or request in the message input and press Enter (or click Send). The AI assistant reads your message, processes it, and replies directly in the conversation thread.
Be as specific as you can in your first message. For example, instead of “I need help,” try “What housing support services are available in Berlin for refugees?” The more context you provide, the more relevant the response.
5

Explore other features (optional)

Once you have had your first AI conversation, you can explore the rest of the platform:
  • Video meeting — Join a Jitsi video call with an NGO staff member directly from the platform. Meetings can be recorded for later reference.
  • Blog — Read resources and news published by NGO administrators. If you have the org_admin role, you can also create and publish posts.

​
Troubleshooting

Double-check your email address and password. If you have forgotten your password, use the password reset link on the login page. If the issue persists, your account may not yet be activated — contact your NGO administrator.
Make sure you are still logged in — JWT tokens expire after a set period and you may need to refresh the page or log in again. If the issue continues, your organization’s AI model may be temporarily unavailable; contact your administrator.
Admin features are visible only to accounts with the org_admin role. If you should have admin access, ask your organization’s administrator to update your role and log out and back in to pick up the change.
Make sure your browser has permission to use your microphone and (optionally) camera. Try a different browser if the issue persists, and check that your network is not blocking WebRTC traffic.

​
What’s next

AI Assistant

Learn how to get the most out of the AI assistant — configure behavior, choose a model, and manage conversation history.

Authentication

Understand how JWT-based authentication ties together the chat, blog, and video features under one identity.

Video Conferencing

Join browser-based Jitsi meetings with NGO staff, with optional recording for case follow-up.

Blog & Content

Read and publish resources on the WordPress-backed blog with role-based access.