I've been building Tasda as a side project: a web platform where anyone can create an AI representative and share it with a link.
What it does
- A guided wizard collects the representative's description, behaviour rules, scenarios and capabilities. No code.
- Knowledge comes from the owner's own documents and links.
- Visitors talk to it by text or voice and can leave service requests for the person behind it.
- The interface and representatives work in English, German and Turkish.
Why
People who share knowledge or services online can't answer everyone around the clock, and generic chatbots don't sound like them. I wanted each representative to feel like the person or character who designed it.
Try it
https://tasda.com/en/ — new users get free starter credits. A few public examples: English Buddy (English conversation practice) and Startup Critic (feedback on startup ideas).
Feedback on the creation flow is very welcome.
Top comments (3)
Free starter credits and service-request handoff are the contact half. When you invent demo owners and requesters for that path, use reserved fiction phones (US 555-0100 to 555-0199, UK 020 7946 0xxx) and domains you control. If you email the owner about a new request, treat the address as contact data: MX / Null MX first (timeout = unchecked).
Thanks for flagging the demo-data and email-validation concerns. Did you encounter a specific example while trying Tasda, or is this a recommendation for testing the request flow? If you saw an issue, the page and steps would help me reproduce it—please leave out real phone numbers and private email addresses. I have not yet verified MX/Null MX handling, so I do not want to claim that check is already in place.
Thanks for the careful question. I was referring to a test path rather than a live issue, so there is nothing specific to reproduce yet.