Company information and services

At Soylu Sistem, we build systems for your business that automatically handle repetitive, time-consuming work. Using AI and taking your way of working into account, we design these systems to reduce manual work, improve follow-up, and give your team more time for important tasks. Important decisions remain in your hands.

To build a useful system, we first need to understand how the work is done today, where it takes time, and what result you expect. We then identify which steps can be automated and which need your review or decision.

We build the solution around your business tools, information, and rules. One simple step may need a connection between two applications, while another may use AI to understand text or a document. The approach depends on what that particular task needs.

Handling customer enquiries, managing email, processing documents, answering questions in text, preparing price estimates, and answering questions by voice are six specific uses of our services. If your need does not fit exactly into one of these categories, you can describe it for review; feasibility and the scope of our commitment are determined after we understand the work.

Automation means that software carries out specific steps people currently do by hand, following the business's methods and rules. For example, receiving an enquiry, taking the necessary information from it, and preparing it for follow-up can be handled through a defined process.

Imagine a customer enquiry arrives by email. An employee reads it, identifies the subject, enters the information into an application, and forwards it to the right colleague. In an agreed implementation, the system can perform these steps and show the employee anything incomplete or requiring a decision. Exactly which steps it will perform is determined before we build it.

AI helps with tasks such as understanding free-form text, identifying the subject, reading information from a document, and preparing a response. Calculating amounts, checking required information, and permitting an action must follow clear system rules. A simple task with fixed rules may not need AI at all.

You decide what the system can do on its own and what should come back to you or the person responsible for approval. Not every step needs manual approval. Clear, authorised tasks can proceed automatically; sensitive, unclear, or unauthorised cases must stop for review.

Before implementation, we agree on a measure suited to the problem, such as the time spent handling each enquiry, the number of manual data entries, or the number of incomplete cases. The goal is to reduce manual work and improve follow-up. The actual improvement must be assessed using that business's own data.

Work that repeats, follows a reasonably clear process, and produces a result that can be checked is usually a better starting point. If the volume is low, the process keeps changing, or the necessary information is unavailable, improving the manual process or choosing a simpler solution may be the better option.

This service suits a business that receives questions and enquiries about its services and spends time understanding each visitor's needs and preparing follow-up.

Using the company's approved information, the assistant can explain services, discuss the visitor's needs, and ask for missing essential information. It then prepares an organised summary of the enquiry and a suggested next step for the sales representative to review. Enquiries are prioritised using agreed rules; this priority is not a definite probability of purchase.

The business receives an enquiry ready for follow-up, with the necessary information. In a connected implementation, it is recorded in an agreed customer management application or shared file. Recording is reported as successful only when the destination tool confirms it.

To begin, we define the service information, essential sales questions, follow-up rules, and where enquiries will be recorded. Meeting bookings, follow-up messages, and additional connections must be separately specified in the scope of work. This service does not guarantee sales or replace the company's entire sales process.

This service suits a business that receives repetitive emails each day and spends considerable time reading them, identifying their subject, and writing an initial reply.

The system can categorize an email, highlight key points and missing information, and prepare a suggested reply that follows the company's rules. The person responsible sees the text and can edit, approve, or reject it.

The output is a useful category and summary for each email, together with a draft reply. A draft is different from a sent reply; automatic sending is not the default for this service and requires separately defined permissions and testing.

To begin, we define one mailbox, message categories, examples of permitted replies, and the person responsible for review. Complex attachments, multiple mailboxes, or automatic sending must be assessed before any commitment. An actual connection to the company's account is made only with authorised access.

This service suits work where information from invoices, purchase orders, or similar documents is regularly entered into a file or application by hand.

In the basic scope, the system extracts specified information, such as the document number, date, items, quantities, and amounts, from a PDF with selectable text. It then checks required information and calculations such as item totals, and flags incomplete or inconsistent entries for correction. Missing information must not be filled in by guessing.

The output is organised information ready for review. The person responsible checks and approves it; the agreed file or output is then prepared. Creating a file is different from recording information in accounting software, and each connection must be specified in the scope of work.

To begin, we define the document type, fictional samples, required information, and one specific output. Scans, document photos, handwriting, multiple formats, and accounting entries require separate assessment and pricing. This system does not make specialist judgments about a document's legal or tax validity.

This service suits a business with recurring questions whose correct answers are available in its service descriptions, guides, or company policies.

The visitor asks a question in everyday language. The assistant prepares its answer from that company's approved information and identifies the source when one can be shown. If it does not have a reliable answer, it must say so clearly or prepare a request for human review.

The visitor receives an understandable answer and a clear next step. In a connected implementation, an unresolved question can be recorded in an agreed support destination. Preparing a summary is different from actually recording a request.

To begin, we define the permitted sources, topics the assistant can answer, the person responsible for approving content, and the route for referral. Access to customer account details, order status, or internal documents requires a specific connection and permission. The assistant cannot know a customer's private status from general knowledge.

This service suits a business where selecting the right product or service, reviewing add-ons, and calculating prices are recurring parts of sales work.

The request is received through a form or a connected dedicated email address. The system checks the required information and prepares an itemised estimate using the approved price list and rules. AI can help understand the need and suggest a product or service; amounts and discounts must be calculated using clear rules.

The output can include a service breakdown, the assumptions behind the estimate, and a pro forma invoice file. This service does not require a chatbot. An initial estimate does not mean a contract, acceptance of an order, or a final commitment to a price; its status and validity must be clear.

To begin, we define base prices, add-ons, tax where applicable, discount conditions, and cases requiring review. A real price cannot be stated as valid until the official price list has been approved. Sending an email reply also requires a separate connection, permission, and test. The demo's educational prices are not Soylu Sistem's rates.

This service suits a business where some incoming questions and requests can be answered through a short, clear conversation.

The assistant receives what the visitor says, answers from the company's approved information, and, if needed, prepares a summary of the request for a person to follow up. If the meaning is unclear, it asks a follow-up question and does not make promises about something it does not know.

The voice assistant comes with the knowledge it needs; the customer does not also have to buy the text assistant. To begin, we define call topics, language, information for answers, sensitive cases, and the referral route. Handling emergencies or making specialist decisions is not part of the assistant's default authority.

The base service is a browser voice conversation. You can try the published voice demo on this site with microphone permission. Start from the voice demo page and use a fictional business question. Telephone numbers, transfers and bookings require separate assessment.

You explain which task repeats, who is involved, which tools you use, and what the current problem is. Fictional samples are enough for the initial review. If a real sample is needed, we specify the type of information and how it should be received before you send it.

The written proposal defines the workflow, deliverables, exclusions, acceptance checks and price. Payment stages, cancellation and refund conditions are specific to the project agreement. Review those terms before accepting; the website estimate does not set them.

We build the agreed version and test it with suitable samples. We check more than successful cases: incomplete information, inconsistent documents, and a lost connection to the destination tool must also have a clearly defined outcome.

You or the person responsible run several authorised real-world scenarios and compare the output with the agreed need. Rules for responses, calculations, or referrals are refined and finalized within that same scope.

Ownership and usage rights are agreed for each project. The proposal identifies which source files, prompts and documentation are handed over, the rights to use them, and any reusable components or third-party licences. Your content and account access are addressed separately. Confirm any required transfer of rights before accepting the proposal.

We can start with a limited task, provided that it delivers a usable output and has clear acceptance criteria. Further features are added by a new agreement. Limiting the starting scope makes the commitment clear and allows the result to be assessed.

Each service must include the parts it needs. You do not need to buy the sales assistant to buy the email assistant. If you choose several services, we assess whether they can share a connection or component; choosing multiple services does not in itself guarantee a discount or mean that their information is the same.

Current setup estimates, supported scopes and combinations are shown on our Pricing page. Combining compatible services counts shared setup work once. Use the calculator for current amounts, then confirm the final scope and fee in writing. Provider usage, hosting and taxes are separate.

Setup, optional monthly support and provider usage are separate budget items. The Pricing page shows current support allowances and extra-connection estimates. Support covers the agreed maintenance and small changes; new features, provider usage and emergency or round-the-clock cover need separate arrangements. The proposal defines support terms, the usage budget and what happens when a limit is reached.

A small pilot and a rollout of several connected services have different timelines. The proposal sets milestones, review points and delivery dates after the scope, account access and approved content are clear. Delayed access or a change in scope can change the schedule. Support and later changes are scoped separately.

For the initial review, a description of the task, the tools you use, an approximate volume, and the desired result are enough. Do not enter customer information, passwords, or access keys into a public conversation or demo. Any necessary access is obtained later through a defined route appropriate to that task.

Hosting and AI providers are selected for your project; the providers used by this website are not an automatic commitment for your system. Before real data is used, the project needs a clear record of processing and storage locations, access permissions, encryption arrangements, retention, backups and recovery. Required data-transfer arrangements are assessed for the selected services.

The business manager approves official information and permitted rules. When prices, services, or policies change, the relevant content must also be updated and reviewed again. Using shared software components does not authorize sharing information or access between different companies.

No. To define your need, you only need to explain how the work is done today and what result you want. The details needed to use the system are taught at handover. The type of training and who it is for are specified in the project scope.

Start with the task that repeats most often or causes the most difficulty. Tell us where the information comes from, who does what with it today, and what output you need. That description can help identify the right approach or the need for further assessment.

In many projects, we first assess whether we can work with the existing tools. A connection to any application depends on its features and available access. If a direct connection is not possible, the alternative route and its cost must be clear before implementation.

Yes, within a scope that has been defined and tested in advance. For example, valid information can be recorded automatically while a sensitive reply is returned for approval. The level of authority depends on the task, the consequences of an error, and your rules.

The manager does not need to review everything personally. You define who reviews the work and which cases need approval. Human review is part of the basic email management and document processing services; changing that approach requires the relevant agreement and testing.

AI output can be wrong. The workflow needs agreed validation checks, human review for consequential or uncertain actions, and a clear way to report and correct errors. Acceptance criteria, responsibility for fixes and support or liability terms belong in the project agreement. The service does not promise error-free AI or guaranteed financial results.

The system must make clear which step was not completed and what needs follow-up. Having a reply or file ready is not the same as successfully recording or sending it. The project defines how retries and unfinished cases are handled.

No. Goals and measures can be defined, but the result depends on the business's circumstances and the actual implementation. Before measuring results, we do not state guaranteed savings percentages, sales increases, or returns on investment.

Automated processes can be configured to work at the times you need. This depends on service availability and maintenance arrangements. The system being available does not mean that the person responsible is available around the clock for human follow-up.

The sales assistant focuses on understanding needs and preparing a sales enquiry. The support assistant is designed to answer from company sources and handle recurring questions. Some knowledge may be shared, but their outputs and follow-up paths differ.

That service is assessed and delivered with the knowledge and components it needs. Buying the text chat interface is not a condition. Telephone connections, voice quality, and the referral route each have their own requirements.

Yes, if the necessary accounts, information, and permissions are compatible. The scope of the connection and responsibility for each step must be clear. Combining services does not automatically authorize broader access, message sending, or commercial commitments.

The required language is defined at the start, and the text, sources, and samples in that language must be reviewed. Content approval or a successful test in one language does not confirm quality in every language. Speech and pronunciation quality also need specific testing.

Yes. The update method and the person responsible for approval must be defined at handover. Some changes involve editing content; others, such as changing a calculation or adding a connection, need technical work. Whether they are possible and what they cost depend on the agreement.

Explore all six interactive demos on this site, including text chat and voice conversations. Each tool explains its inputs, outputs and actual limits. Use fictional examples. These are demonstrations, not client projects or measured financial results; a system for your business needs its own configuration, permissions and testing.

The company's legal name is Soylu Sistem, registered as “Soylu Sistem İç ve Dış Ticaret Ltd. Şti.” The company's stated location is İstanbul, Türkiye.

Email info@soylusistem.com with a short description of the repetitive task, your current tools and the result you want. This helps us assess a useful starting scope and discuss the next step. Do not include passwords, confidential files or unnecessary personal details. Our website is https://soylusistem.com.