Farvahar Tejarat Pars
Corporate site without a cart. What you can verify is the live site.
Emergency breakage and scheduled maintenance are different jobs. One investigates a broken function. The other puts updates and checks on a calendar.
Choose one-time technical support when the site is down, forms fail, login breaks, an update breaks pages, SSL/domain issues appear, or a WooCommerce checkout/order flow stalls. Choose ongoing maintenance when you need planned updates, backup routines, health checks, and limited small changes under an agreement.
Speed-only WordPress work belongs on WordPress optimization. A new site belongs on WordPress design or web design. Platform change belongs on WordPress to custom. New products belong on custom development or web applications. Store builds belong on e-commerce.
| Situation | How we usually treat it |
|---|---|
| Site down or critical error | One-time technical review |
| Forms or admin login broken | One-time functionality check |
| Breakage after an update | Backup discussion, then compatibility work |
| SSL, domain, or hosting symptoms | Access and configuration review |
| WooCommerce order/payment flow stuck | Store flow investigation (third parties may apply) |
| Update and backup schedule needed | Ongoing maintenance plan |
| Small copy or layout tweaks | Within plan allowance if agreed |
| Custom app existing features | After stack assessment |
Items apply only when written into the engagement. Not every technology or request is automatically supported.
Absolute security, successful malware cleanup, and guaranteed uptime are not promised before assessment. Hosting providers, payment gateways, and external APIs may require separate coordination. Deep performance campaigns belong on WordPress optimization.
Pick the model that matches the problem. Coverage, response expectations, and allowances are defined in the written agreement — not invented as a public SLA on this page.
Depending on the agreement: scheduled updates, compatibility checks, backup management, periodic health checks, bug fixing within scope, limited maintenance notes, and small changes within an agreed allowance. Hours, ticket limits, monitoring frequency, and response windows are only valid when written into the contract.
| Model | Best for | Typically outside |
|---|---|---|
| One-time technical support | A specific error, conflict, or urgent breakage | Ongoing monthly care |
| Ongoing website maintenance | Scheduled updates, checks, and limited small work | Unlimited requests and new products |
| Maintenance + small development | Care plus a defined allowance for minor changes | Features that exceed the allowance |
| Custom agreement | Critical stores or applications needing tailored terms | Undocumented emergency response |
IlyaWeb can assess and, when appropriate, support websites originally built by another developer or agency.
Requirements for a serious handover: the technology stack must be identifiable; appropriate access must be available through an agreed secure method after initial contact; existing code and infrastructure must be assessable; third-party dependencies may limit what can be supported; scope and estimate depend on findings.
Do not send passwords through the public contact form. After we confirm the inquiry, we agree a secure way to exchange credentials. We do not claim we can take over every legacy system without limitations.
Some issues resolve quickly; others need deeper investigation. We do not publish fixed resolution times without a written agreement.
Share URL, symptoms, platform type, and preferred contact. Without access, diagnosis stays limited.
Separate urgent breakage from maintenance items and clarify priorities.
When needed, obtain agreed access and investigate logs, plugins, hosting, or code.
Written work list and a USD starting estimate or custom quote before major changes.
Work proceeds after approval. Backups are discussed before critical updates.
Confirm the reported issue and related key flows within the agreed scope.
Handover notes. Periodic reports only when the agreement includes them.
International support uses a starting estimate or custom quote in USD. See pricing factors.
The public address of the site that needs help.
WordPress, WooCommerce, custom, or “not sure.”
What broke, when it started, and what you already tried.
Optional preferred timeframe — not a guaranteed SLA unless contracted.
Creating a backup is not the same as proving a restore. Both are written separately when needed.
Before critical updates we discuss backups and rollback. Live changes are tested when a staging environment exists — not every host provides one.
Domain, hosting, paid plugins, and third-party service fees are usually billed separately. Major redesigns, migrations, and new products are outside routine maintenance. Response times and emergency handling apply only when written into the agreement. 24/7 intervention is not a standard promise on this page.
We do not publish a fake package price list. After review, international clients receive a starting estimate or custom quote in USD.
Iranian-market package prices on other language pages are not automatically applicable internationally unless explicitly confirmed. Maintenance fees are distinct from hosting, domain renewal, third-party licenses, and major development work.
| Factor | Why it matters |
|---|---|
| Website type & complexity | WordPress, WooCommerce, and custom stacks differ |
| Problem severity | Urgent breakage vs scheduled care |
| Access & investigation depth | Logs, staging, and third-party coordination |
| Number of requested changes | More items expand testing |
| Integrations | Payments, APIs, and external services |
| Maintenance frequency | Monthly workload and update cadence |
| Agreed allowance | Hours/tickets only if written into the plan |
| New development | Features beyond maintenance need a separate quote |
IlyaWeb has representative offices in Dubai, London and New York. Collaboration is remote. Representative offices in Dubai, London and New York. In-person visits by appointment only.
Trust comes from written scope, clear handover notes, and honest limits — not invented uptime percentages, awards, or unverified testimonials. Sites built by other teams are welcome after assessment.
Related services stay distinct: WordPress optimization, WordPress design, custom development, migration, and web design. Company context: About IlyaWeb.
These sites are online. Screenshots show each homepage. They were delivered in Iran and are not presented as local client references for other markets.
Corporate site without a cart. What you can verify is the live site.
Live insurance brokerage site. We do not publish policy counts or conversion rates.
We do not invent client names, rankings, traffic, or revenue. Request a consultation
Whatever is written in the agreement — often updates, checks, bug fixes within scope, backup routines, and limited small changes. Service cards on this page are candidates, not automatic inclusions.
Cost depends on site complexity, urgency, access needs, integrations, maintenance frequency, and any development allowance. International quotes are in USD after review — not a fake list price here.
Yes, including many WordPress and WooCommerce sites after assessment. Not every plugin stack or hosting setup is automatically supportable without review.
Product, checkout, order, and related flow issues can be investigated. Payment providers and hosting may require separate coordination.
Often yes, after we identify the stack and obtain agreed secure access. We do not claim ownership of unseen code before assessment.
Yes. One-time support is for a defined problem with assessment, estimate, implementation, and handover.
Yes. Ongoing plans are written agreements covering scheduled care and defined allowances — not unlimited free work.
Yes, when the cause is within the site/stack we can access. Some issues originate in hosting, DNS, or third-party services.
Basic checks, hardening, and backup planning can be included when scoped. Absolute security and guaranteed malware recovery are not promised before assessment. Backup and restore are separate tasks.
Yes, subject to stack assessment. We do not automatically support every framework or legacy system.
Usually no. Hosting, domains, and third-party licenses are typically separate from IlyaWeb maintenance fees unless the agreement says otherwise.
Small changes may fit an allowance. Larger features, redesigns, and migrations need a separate assessment and quote.
It depends on severity, access, third parties, and scope. We do not publish fixed resolution times without a written agreement.
IlyaWeb has representative offices in Dubai, London and New York. We collaborate remotely via agreed channels. Scope is written before major work. Representative offices in Dubai, London and New York. In-person visits by appointment only.
Only if explicitly contracted. Default support is not marketed as guaranteed round-the-clock emergency coverage.
In-person visits by appointment only