Meyda Online
Business knowledge in conversation
- Documents and PDFs
- Structured Q&A
- Professional and structured knowledge
Approved information > clear answer
Behind the conversation is a complete system.
How does Meyda.ai
work?
Your knowledge enters the system in a controlled way. Live information connects when needed. Business rules define the boundaries — and Meyda can continue from an answer all the way to an action.
Web management interface
You define what Meyda knows — and how it behaves.
The management interface brings knowledge, context, behavior rules and connected information sources into one place.
Don't just upload a file. Give it context.
When information is uploaded, administrators can explain what the file contains, how Meyda should use it and how important that information is.
The same interface can define behavior rules, the conversation UI and, depending on the selected package, webpages or APIs to scan and how frequently they should be refreshed.
Knowledge uploadDocuments, PDFs, structured Q&A and business information
Active
Context & priorityWhat the information means, when to use it and its relative importance
Defined
Behavior & UIConversation boundaries, instructions and interface settings
Custom
Dynamic sourcesWebpages, APIs and refresh frequency depending on the plan
Connect
One conversation. Multiple information layers.
The question is simple. A controlled process runs behind it.
- The user asks
- Approved knowledge is checked
- Live information is retrieved when needed
- An answer or action follows
Three cumulative layers
Each layer adds capability — without changing the conversation experience.
Meyda Connect
Information that changes over time
- Webpages
- Read-only APIs
- Defined refresh frequency
Information changes > the answer changes
Meyda Act
From conversation to business action
- Collect user details
- Confirmation and verification
- APIs that execute a process
Don't just explain > execute
Advanced rules
Make the conversation behave according to your business rules.
Advanced users can define conversation and decision rules that remain consistent throughout the process.
Example: user preference
Remember how the user asked to be addressed
In languages that use gendered forms, if a user asks to be addressed in the feminine form, Meyda can be configured to preserve that form throughout the conversation.
Example: geographic business rule
Search within a radius — and sort the results correctly
For a service-center search, for example, the rule can require locations within 10 km of the user's reference point and display all relevant results in ascending distance order.
Controlled usage
Define how much, what topics — and when a conversation ends.
Usage controls help reduce excessive, automated or irrelevant use.
Conversation length
Set a maximum length for each conversation.
Conversation limits
Limit the number of conversations per user.
Automatic termination
End a conversation for abusive language or another defined condition.
Topic boundaries
Keep conversations focused on subjects relevant to the organization.
System integration
For the user, it is always one conversation.
Behind the scenes, Meyda can combine managed knowledge, changing information and operational systems according to the selected connection level.
- Embed in a website or mobile application
- Retrieve information from APIs according to permissions
- Execute predefined actions with Meyda Act
- Add user confirmation and verification to sensitive processes
Frequently asked questions
A few more things worth knowing.
Where does Meyda get its information, and does it use only our approved sources?
Your organization defines the approved information sources and conversation boundaries. You can upload documents, PDFs, structured Q&A and business information, and depending on the selected level, connect webpages and APIs. Meyda is designed to answer within the context and knowledge configured for your organization.
How does Meyda keep information up to date?
With Meyda Connect, administrators can define webpages and read-only APIs as dynamic information sources, and set an appropriate scanning or refresh frequency for each source based on how quickly the information changes and the business need.
Can Meyda connect to our ERP, CRM or other business systems?
Yes. Meyda Connect can retrieve information from approved APIs, while Meyda Act can invoke predefined actions. The scope of each integration depends on the APIs exposed by your business systems and the workflow being implemented.
Can Meyda make reservations, schedule appointments or perform other transactions?
Yes. With Meyda Act, a business workflow can collect the required information, present a summary or request user confirmation, and then invoke an approved API to perform the action.
Can we control how Meyda manages a conversation?
Yes. The management interface can define conversation scope, behavior rules, persistent preferences within a conversation, and business conditions that Meyda should apply.
How can we prevent excessive or irrelevant use?
Administrators can set a maximum conversation length, conversation limits per user, conversation scope, and immediate termination conditions such as abusive language or other organization-defined criteria.
Can we customize the design?
Yes. Colors, greeting text and other interface settings can be adapted to your brand and to the environment in which Meyda is embedded.
How quickly can Meyda be added to a website or app?
Embedding the conversation interface itself is simple and fast. The overall implementation time depends on knowledge preparation, behavior rules and the integrations required. In mobile apps, the interface can be embedded using a WebView according to the implementation.
Don't start with AI. Start with the need.
Do your customers still have a question or process they have to handle the hard way?
Tell us what should happen in the conversation. We'll look at the knowledge required, the systems that need to connect and how far Meyda can take the user.
