8. Community and Messaging

Owning an electric vehicle is an experience in which new habits are learned along with the vehicle. Over time, the user discovers which charging points fit their daily routine, how to plan long trips, how their vehicle behaves in different conditions, and where to find services that suit their needs. In this learning process, the experiences of people who have been in similar situations are as valuable as technical knowledge.

A station’s location can be seen on the map; which entrance of the parking lot gives access to it is easier for a driver who uses it to explain. The technical specifications of a vehicle can be published by the manufacturer; another user can share from their own experience the break pattern, luggage use or daily charging habits of a family trip made with the same vehicle.

eBattery Community combines this exchange of practical information with the app’s map, route, trip and vehicle ownership experience. Users can connect with people who speak the same language, drive similar vehicles, live in the same area or are planning a shared trip. Individual experiences turn into a shared body of knowledge that the relevant people can access.

Social Hub Culture in the EV Ecosystem and eBattery's Approach

Social hub, is a center where people regularly meet around a shared interest or need, share information and build relationships. This center can be a physical place, a digital community, or a structure where the two work together.

This culture has a strong counterpart in the EV sector. Vehicle owners experience the same technology in different cities, climates and usage conditions. Their relationship with charging infrastructure, their trip planning habits and their questions about their vehicles all intersect. In this way, the community becomes a space where everyday usage knowledge circulates.

Examples around the world show different aspects of this need:

PlugShare is an example of turning the station experience into shared knowledge. The check-ins users make at charging points, and the photos and descriptions they share, help other drivers reach a location or assess the service there. PlugShare’s own community description also emphasizes the role of user contributions in the station experience, location information and the correction of records.

Tesla Motors Club represents the digital community culture that has formed around vehicle ownership. It describes itself as an independent community, an international space where people of different knowledge levels, from beginners to experienced users, can communicate and share knowledge. This example shows that vehicle owners have a learning and communication need that continues after purchase.

Rivian's Charging Outpost approach makes the physical, social side of the charging experience visible. Rivian describes its Joshua Tree site as a place for rest and connecting with the community alongside charging. In the introduction of the first Charging Outpost near Yosemite as well, seating areas, rest facilities and spatial arrangements that support the journey experience stand out.

Based on these examples, eBattery's product approach addresses three needs together: learning from experience, connecting with similar users, and bringing digital communication together with real journeys.

A charging break can be an opportunity to meet other drivers for those who want it. A brand group can provide a starting point where a new vehicle owner can comfortably ask their first questions. A shared trip plan can turn into a real weekend program organized by friends together. The form and level of participation are up to the user.

User need Value the community can provide Its counterpart in eBattery
Getting used to an electric vehicle Benefiting from similar experiences Groups by brand and model
Learning local usage knowledge Reaching region-specific experiences Communities by language and market context
Preparing a trip Evaluating route and break options together Route and trip cards
Following a specific topic Finding related conversations in one place The Topic structure
Connecting with other drivers Building communication around shared interests Username, friendship and direct messaging
Following the industry Accessing content with visible sources News and content integration

Community and basic messaging are parts of eBattery’s current Web2 product scope. News sources, in-app sharing cards, and expanding group tools gradually deepen this experience through links with the relevant modules.

8.1 Language-Based Localization and Automatic Chat Language

8.1.1 Welcoming the user with a community they can understand

In a global app, the starting point of the community experience is for users to find an environment where they can communicate comfortably. Language plays a direct role in building this environment.

When the community screen is first opened at eBattery, the language used in the app is taken as the starting preference. A person who uses Turkish starts discovering Turkish communities, and a person who uses Italian starts discovering Italian communities.

This approach reduces the chance that a user is met with many groups that are irrelevant or hard to understand at first. Asking a question, sharing an experience or reviewing a shared route becomes more natural.

The automatic chat language shapes the initial discovery experience. Users can change this preference and can join communities in other languages of their own accord.

8.1.2 Evaluating language together with local usage conditions

Users who speak the same language may live in different countries. Conversely, users living in the same country may prefer to communicate in different languages.

eBattery's localization approach treats these two dimensions separately:

  • Language, defines the language in which the conversation is conducted.

  • Country or region context, explains where the services mentioned and the terms of use apply.

For example, a Turkish-speaking user living in Germany can join a Turkish EV group. However, the fact that the charging experience they share relates to an operator in Germany is important context when assessing the information.

Similarly, the equipment or software features of the same vehicle model may vary across markets. Making group and topic names clear about these differences reduces the wrong generalization of experiences.

A language preference is not turned into an assumption about the user's citizenship or identity. Users decide for themselves which communities they want to be in.

8.1.3 Managing app language and community language independently

Users can change the community discovery language without changing the app's interface language.

For example, while continuing to use eBattery in Turkish, a user can reach an English-speaking community. This makes it possible to take part in international experience sharing while using the map, account and route screens in the language they are used to.

English is treated as the language of international communication, without being limited to a single country. Other languages are also offered within the cultural and local context of the relevant communities.

Changing the community language does not cause the user to leave groups they joined earlier. Memberships and discovery preferences are managed as separate functions.

8.1.4 Distinction between “Joined” and “Discover”

The main Community experience brings together the user's need to keep up with existing connections and to discover new groups in two separate areas.

Field Content Convenience it offers the user
My Joined All groups the user is a member of Access to memberships in different languages from one place
Explore Discoverable official groups in the selected language Reaching new communities on a regular basis

A user who is a member of Turkish and English groups sees their groups in both languages under "Joined". When they change the discovery language to browse new French communities, their existing memberships are kept.

This structure makes it easier for users to expand their community over time. Language selection stops being an action that has to be repeated constantly to get access.

8.1.5 Building local community density

The benefit of a community depends on enough interaction forming for users to respond to one another and meet around shared topics.

eBattery's starting approach is to bring users together in meaningful group and topic structures. Rather than opening many spaces that closely resemble one another, discussing shared needs in the same place strengthens the accumulation of knowledge.

As the community grows, new brand, model or regional needs can be met with separate spaces. This expansion is addressed together with actual usage and content density.

The aim is for the user, on opening the app, to reach relevant people to talk with and meaningful content to follow.

8.2 Official Groups and User Groups

8.2.1 The role of official groups

Official groups are shared spaces created by eBattery and managed within the platform's community structure. They help new users understand which groups they can join and reach the main topics easily.

These groups can be organized around different needs, such as a brand, general EV use, local experience or industry news.

The The word "official" indicates that the group is created and managed by eBattery. In a community named after a vehicle brand, an authorized account speaking on behalf of the manufacturer is a separate representation relationship. A group name alone does not constitute a manufacturer partnership or authorized service status.

This distinction helps users correctly assess the source of the information they encounter.

8.2.2 User groups and invitation-based participation

User groups support smaller communities formed around a specific purpose.

Friends who will travel together, drivers living in the same city, or people who want to share a common vehicle experience can create their own communication spaces. Alongside broader communities, these groups make room for closer relationships and a specific agenda.

For user groups, the basic way to join is an invite link. The group grows through the participation of invited people, independently of the public discovery list.

Joining by invitation helps keep the group’s purpose and membership framework more controlled. At the same time, it is taken into account that an invitation link can be shared; the group admin manages the group’s access arrangement and memberships.

Feature Official eBattery groups User groups
Purpose of establishment Creating an organized community space for shared EV needs Communicating for a specific circle or purpose
How it is discovered Discovery area within the relevant language and category Invitation link
Management eBattery's community management The group owner and the admins they authorize
Content layout The platform's group and topic templates An arrangement consistent with the group’s purpose
Common framework The platform’s community rules The platform’s community rules

8.2.3 Community value across the user lifecycle

It is important for an EV community to bring together users at different experience levels.

A new vehicle owner may be trying to understand the basics of everyday use. Someone who has driven an electric vehicle for a long time may want to discuss a new software version, a particular route or a different charging experience.

These two groups of users contribute to each other. New users' questions lead experienced people to explain things they now do automatically. Experienced users' posts also make the learning process easier for beginners.

eBattery adopts a community language that supports this relationship. Being able to ask basic questions freely, explaining technical terms clearly and respecting different usage conditions strengthen participation.

Describing the conditions under which a particular experience took place is just as valuable as sharing a model's longest range or lowest consumption.

8.2.4 Community management and contribution quality

Group moderation works to keep order, keep conversations on relevant topics and let users communicate respectfully with one another.

Criticism is an important part of the service experience. Sharing a negative experience about a station, a vehicle feature or a service can contribute to building knowledge on the subject. The factors considered in the review are that the account is relevant, that personal information is protected, and that users are not singled out.

Community development is not assessed solely by the number of messages sent. Questions getting answers, explanations being useful, recurring issues accumulating under the relevant topics and new users joining are more meaningful indicators.

This approach is kept for connections built with gamification as well. Community quests are designed to support useful contributions defined by program rules, rather than mechanics that encourage spam. A game level or point is not presented as an indicator of technical expertise.

8.3 Topic Structure and Brand Templates

8.3.1 Preserving the context of conversation in large groups

In a brand group, software updates, accessories, charging experiences and service processes may all be discussed at the same time. When all messages are collected in a single stream, it becomes harder to follow a particular topic.

eBattery’s Topic structure creates topic-focused spaces within the main group. The user can stay a member of the main community while joining the conversation on the subject they are interested in.

This arrangement balances everyday chat with the sharing of information that may remain useful for longer, within the same community. While one user discusses a new accessory, another can follow technical experiences related to their own model.

Topic headings make visible what need the information is being shared for.

8.3.2 Brand- and model-focused templates

eBattery uses adaptable topic templates to create a familiar structure across different brand communities.

Communities for brands such as BYD, Tesla or Togg can be organized around their own model structures and local usage needs. The structure below shows a sample topic template for brand groups:

Topic Content scope
General Chat Everyday communication and general experiences within the Community
Model-Based Topics Posts about specific vehicle models and suitable variants
Software and Apps Vehicle software, mobile app and update experiences
Charging and Long Trips Stations, break planning and trip experiences
Service and Spare Parts Maintenance, service processes and parts experiences
Problems and Solution Experiences Situations users encounter and processes they follow
Coating and Protection Vehicle protection applications and user experiences
Accessories Vehicle-compatible products and user reviews

The purpose of the template is not to force all brands into the same details. While a common navigation logic is provided, topic names are adapted to the needs of the relevant brand and community.

When a user moves to a different brand group, they recognize the basic layout; model and usage details are shaped according to that community.

8.3.3 Making experiences comparable

In the EV experience, context determines the meaning of information.

Different battery options, production years or software versions of the same model can lead to different results. City use and long-distance consumption also do not represent the same conditions.

The topic structure supports users in sharing their experiences together with these details. In a consumption review, stating the vehicle variant, trip type and measurement conditions helps other users make a more accurate comparison with their own situation.

A statement like "my car uses this much" becomes more useful information once its conditions are explained. Likewise, a software change appearing in a particular market or version does not mean that all users will have the same experience.

The community provides a space where these differences can be discussed and clarified.

8.3.4 From everyday conversation to lasting knowledge

Well-organized topic areas let experiences related to specific needs build up in one place.

A conversation about home charging can regain value a few days later for another user with a similar need. The rest-stop arrangement of a route or how a service process went can be put in context more easily under the relevant topic.

The date of information matters too. An explanation belonging to a previous software version, or a station condition that was valid in the past, should be evaluated alongside the current status. Date and source information support this distinction.

In this way, the community builds up, over time, a regular body of experience from which users can learn from one another.

8.4 News and Content Integration

8.4.1 Linking the industry agenda to user needs

Developments in the electric vehicle ecosystem can affect users' everyday decisions. New vehicles, software updates, charging network openings, product reviews and service changes are published across different sources.

eBattery's news and content area lets this content be discovered within the relevant communities. While following the industry agenda, the user can also consider other drivers' experiences on the same topic.

Content selection is linked to language and local market context. Charging network development in a particular country may have more direct meaning for people who drive in that region. A vehicle update, on the other hand, may produce a more useful discussion in the relevant brand or model community.

8.4.2 Content cards with visible sources

News integration is set up through a suitable API, RSS or other sharing methods supported by the publisher.

Content is presented with its title, source, publication date and a link to the original publication. The use of short descriptions, images or previews is carried out in line with the scope and terms of use provided by the relevant source.

The basic information on a news card is as follows:

  • The title of the content.

  • Broadcaster or content creator.

  • Publication date.

  • The relevant language and topic.

  • A short description or preview, where appropriate.

  • Link to the original content.

This structure keeps the source that produced the content visible. When the user wants to review the details, they can reach the original publication.

8.4.3 Distinguishing news, commentary and commercial content

Within the community, different types of information can exist around the same topic. A manufacturer's announcement, a content creator's review and a user's personal experience have different source relationships.

eBattery aims to keep the nature of content clear:

Content type Source relationship disclosed to the user
Manufacturer or operator announcement The relevant organization’s own statement
News content News prepared by the publisher
Review or comment Content creator’s assessment
User experience A community member's own observation
Sponsored content Sharing offered within a commercial relationship

A heading in a piece of content does not, on its own, mean that the information has been independently verified. Users should be able to reach the source and the scope of the disclosure.

This distinction also matters when the publication date differs from the date of the development described in the news. When an old piece of content is shared again, it should not be treated as a current announcement.

8.4.4 Linking content to the relevant conversation

News can start communication among users about the topic.

When a software update is moved to the relevant model heading, users can share the changes they see in their own vehicles. Content published about a new charging point can be enriched by the access and usage experiences of users in the area.

This link ensures that the published information and the experience people have had are handled in the same context. While discussing the content, users can still reach the source link.

Partners and local businesses can also share relevant information with the community. These contributions are made in line with the group's topic and content rules; commercial posts are clearly identified.

8.5 Direct Messaging, Username and Search

8.5.1 Moving from the shared space to personal communication

Group conversations support shared information, while one-to-one messaging offers a more suitable space for communication between two users.

Asking for details about a shared route, discussing the meeting time for a trip to take together, or exchanging experiences with someone who uses the same vehicle model are examples of this flow.

The user can move to messaging from the relevant person's profile. Whether contact can be made is assessed together with the other party's message acceptance settings.

This structure allows a relationship that begins in the community to continue within the app.

8.5.2 Unique username

In eBattery, a unique username makes it easier to find people and reach the right account.

There may be users with the same visible profile name; the username is the identifier that distinguishes the account. Within a group, it can be used to mention a person, search, or start a message.

Communication based on usernames reduces the need to share additional contact details, such as a phone number, with other people.

In the technical structure, the username is linked to the account's fixed internal ID. When the username is changed, existing chat relationships and past records stay connected to the correct account.

An account being discoverable does not mean that all profile information is public. Profile visibility is managed separately.

8.5.3 Search, profile and friendship

User search provides access to the relevant account via the username. In the search result, the profile can be viewed, messaging can be started within the permitted scope or a friend request can be sent.

Friendship helps users manage their closer circles of communication. Message acceptance or the visibility of certain profile information can be linked to friendship preferences.

A friend request and its acceptance are treated as separate events. Being together in a group does not by itself create a friendship relationship or access to private information.

This distinction lets users define their personal circles of communication by their own choice while joining broader communities.

8.5.4 Moving from the social map to messaging

The social map is another entry point for connecting with users who have turned on location visibility.

When a profile visible on the map is viewed, a one-to-one chat can be started if the other party’s messaging settings allow it. The conversation that opens is linked to the same message history in the Community section.

When the user returns from a conversation started from the map, they land back on the map. When they later open the Messages section, they can continue the same conversation.

Thanks to this continuity, the map and chat do not create two separate communication histories. Wherever the user starts, the conversation is preserved between the same accounts.

Sending a message from the map does not require automatically passing the sender's location to the other party. Location sharing is managed with its own visibility and sharing settings.

8.5.5 Shared access to AI Chat

The fixed AI Chat entry in the community area provides access to eBattery's central assistant.

When a user wants to prepare a route, plan a trip or review an existing result during a conversation, they can switch to the same AI experience. The prepared content is shared with the relevant person or group at the user's choice.

AI chat is visually and functionally separated from messaging with people. The presence of the assistant is not implemented as automatically passing private messages or whole group conversations to AI.

The user decides which information they want to work on with the assistant or share with others.

8.6 Message Types — Including Route, Trip and Efficiency Cards

8.6.1 Communication formats suited to EV use

The experience users want to describe does not always fit into a short text. Showing a station entrance with a photo, sharing a meeting point as a location or conveying a long explanation with a voice message can be more useful.

eBattery’s messaging structure brings different content types together in a common conversation flow.

Message type Usage example
Text Asking questions, sharing experience and everyday communication
Photo and video Sharing images related to a station, vehicle or product
File Providing the relevant documents
Voice message Describing the experience with a voice recording
Location Sharing a meeting or visit point
Route card Sharing the route and planned stops
Trip card Sharing a visit schedule divided into days
Efficiency card Sharing the selected period and indicators
Product link — after EV Market Redirect to the relevant product page in the app

Content types work with appropriate access rules in the context of group and one-to-one messaging.

8.6.2 Route cards: Sharing without rewriting the plan

The route card lets a route created in the app be shown in the chat as a clear preview.

Depending on the sharing scope, the card may include start and destination information, a route summary, distance, estimated duration and planned charging stops. By opening the card, the recipient can go to the relevant route details.

This structure reduces the need for the user to describe the whole route again within a message. The conversation can continue on the same plan.

The vehicle context of a shared charging plan also matters. A stop layout prepared for a vehicle with a large battery may not suit a vehicle with a different capacity in the same way. When the recipient wants to use the plan on their own trip, it is re-evaluated using their own vehicle profile and current battery information.

Likewise, past availability or price information on the card is not considered current at the time of later use. When moving on to the transaction, the accessible data is refreshed.

8.6.3 Trip cards: Making the shared plan easy to talk about

Trip cards allow a multi-day program to be shared while keeping it intact.

Users can send their plan, including the trip region and daily stops, to a group of friends. Recipients can review the schedule and discuss a specific day or place to visit.

For example, when a user prepares a two-day Cappadocia plan, group members may want to add a different visit to the second day or change the break time. The edit is handled on the relevant planning screen, and the updated plan can be shared again.

This experience preserves the link between the conversation and the plan. Users work from a specific plan rather than piecing the same trip together from different fragments of text.

It is also important to understand which version the shared content belongs to. Not confusing an old card with a newly edited schedule ensures that users planning a trip together rely on the same information.

8.6.4 Efficiency cards: Sharing the result together with its conditions

The efficiency card lets the user share the indicators they choose in the chat. The purpose of the card is to make visible the period and data scope on which the comparison is based.

The following information may be included in the share, within an appropriate scope:

  • Evaluation period.

  • Vehicle information the user chose to share.

  • Distance and energy indicators.

  • Distinction between measured and estimated data.

  • The related short review.

One user's low consumption value is not presented as an achievable result for everyone making a different trip. Vehicle, route, usage and measurement conditions affect the comparison.

For this reason, the cards carry the numerical result together with its context. This helps users interpret their experiences more accurately and discuss them constructively.

8.6.5 Seeing the scope of content before sharing

Route, trip and efficiency records may contain personal information. A home address, regularly visited locations or detailed trip history are not needed for every share.

eBattery’s sharing approach is based on the user being able to see in advance the content they will send and manage the scope of information involved. Sharing a plan card does not mean granting access to the entire history in the account.

Likewise, a single location sent in a message is a different action from enabling continuous location visibility on the social map. The user is clearly shown what the share includes.

When a card is opened, authorization to access the relevant content is also checked. Simply having a link does not grant the right to access all the private details of the content.

8.6.6 The sharing experience expanding with EV Market

When EV Market is activated, product links may connect community conversations with the shopping experience.

A user can share a charging cable or vehicle accessory in the relevant topic. The recipient can review the product's technical specifications, vehicle compatibility and sales terms on the product screen.

Community comments and the product's verified technical information are presented with their separate meanings. A user being satisfied with a product is not treated as proof of compatibility for all vehicle variants.

This link turns shared experience into a source of information that contributes to the purchase decision, while the product review keeps its own scope.

8.7 Privacy, Blocking and Notification Settings

8.7.1 Presenting participation together with visibility controls

Users being able to join the community comfortably depends on their being able to manage what they share and with whom.

eBattery’s social experience handles preferences such as message acceptance, profile visibility, online status and location sharing with separate controls. A user using one feature does not open all social visibility areas at once.

Control area Preference managed by the user
Direct messages Whose messages are accepted
Profile photo Which user circle the photo is shown to
Online and last seen information Visibility of the relevant status information
Social map Whether location visibility is on or off, and the scope of sharing
Blocked accounts Managing unwanted one-to-one contact
Group and personal notifications Which conversations create notifications
Notification types Preferences for DM, mention and friendship events
Community language Language used on the discovery screen

These controls let users adjust their level of social participation to their own needs.

8.7.2 Blocking, muting and reporting

Blocking, muting and reporting respond to different needs.

Blocking, is used to stop unwanted one-to-one communication from the relevant account. Blocked accounts can be managed from a separate list.

Mutelets you control the notifications of a conversation. The user can stay in the group and open the conversation whenever they want.

Report, starts the review of a piece of content or an account under platform rules. The user can create a report linked to the relevant message.

The visibility of content published in shared groups is handled together with the group's access and content rules. Live location visibility is also managed through its own settings. What area each control affects is explained clearly to the user.

8.7.3 Organizing notifications by importance and context

As the community grows, receiving a notification for every message can tire the user. The notification system should help the user focus on the communication they want to follow.

The main notification events are:

  • New direct message.

  • Mentioning a username in a conversation — mention.

  • Friend request.

  • Accepting a friend request.

Group, person and notification type preferences are considered together. Details such as mention behavior in a muted conversation are shown clearly in the selected notification settings.

The user can choose to be informed of communication directed at them without having to follow every conversation in a broad brand group in real time. They can set up a quieter usage pattern for another group.

Notification content is also handled within the scope of personal data. Message previews that can be displayed on the lock screen are managed in line with user and device preferences.

8.7.4 Location sharing being clear and controlled

Social map visibility depends on the user’s preference. Using location to find nearby charging points and showing location to other users are separate purposes.

When a user turns off social visibility, the principle is that new location sharing is stopped. A location previously sent within a message is treated separately, as the content of that conversation.

This distinction explains the scope of sharing to the user correctly. Turning off live visibility does not mean that information previously passed on to another person becomes as if it had never been shared.

The same approach applies to route and trip cards. The content of a shared plan and the user's live activity are managed independently of each other.

8.7.5 Moderation approach for a trustworthy community

The healthy development of the community depends on the consistent application of clear rules.

Harassment, unauthorized sharing of personal information, impersonation accounts, spam and misleading commercial redirection are assessed under moderation. The review is carried out with the context of the relevant content and behavior.

The limits of the user experience are also preserved in technical discussions. An app that works on one person's vehicle is not turned into a general instruction for all vehicles. On issues requiring technical intervention, manufacturer information and referral to authorized service are kept visible.

Space is made in the community for sharing critical experiences. The existence of a negative opinion about a brand or service is not, by itself, treated as a reason to remove content; the assessment is based on platform rules and the nature of the post.

8.7.6 Privacy strengthening community value

Joining the community does not require a user to make their entire personal life visible. A person can ask questions about their vehicle, share a trip plan and communicate with other drivers, while keeping their location, payment history and private conversations within their own access limits.

eBattery’s social hub approach develops together with this control. People can contribute more comfortably when they know what information they will share and can manage their communication preferences.

The long-term value of the community also depends on the quality of these contributions: a question that gets an answer, a usage experience that becomes clearer, a trip organized together, or an explanation that makes another driver's job easier.

eBattery Community builds an EV communication space where these small but concrete contributions complement one another. What a user learns during their daily journey can, by their own choice, help another user set out better prepared.

Search eBattery

Search for a feature, guide or topic.

Starting pointsFinding a charging station →Sample RWA project →Guides and news →