The contact desk at EXCELLENCE IN COMPUTER PROGRAMMING, INC. takes written enquiries, telephone calls and porch visits by arrangement. A short note describing the system and the concern is the most useful way to start, and it will receive a written reply in the order it arrives.
Every enquiry is read by a member of the porch team, not a queue. If the matter falls within the six services described on the services page, the reply will name the service that fits best and propose a first conversation. If it sits outside that work, the reply will say so plainly and, where possible, point toward a more suitable direction.
Name the systems that run today, the release habit in use and the concern that prompted the enquiry. Three short paragraphs are plenty, and a recent release note is useful if one exists.
Written enquiries are answered within two business days in the order received. Calls placed during business hours are usually answered directly, and messages outside those hours are returned the next working morning.
Yes. The porch office is the home base for boards, build sheets and release notes, and remote working sessions are held with client teams in any time zone, scheduled around the Mountain Time calendar above.
A written note reaches the porch team and is logged the same working day. The first reply acknowledges the enquiry, names the person who will handle it and, where the information allows, suggests one of the six porch services as an opening. There is no sales process on this porch, and no automated sequence of follow up messages.
When a first conversation is scheduled, it usually lasts about an hour. The company asks about the systems that run today, the release habits in use, the people who will own the work afterward and the concern that prompted the call. The conversation ends with a one page intake note naming the next step and the person responsible for it, so both sides leave with something written.
If an engagement follows, the intake note becomes the first task card on a task board bay, and the board is opened with the client team before any code is touched. That habit keeps early assumptions visible and keeps the path from enquiry to delivery short and readable.