Jump to content

atilla.gahbro

Retired Forum Member
  • Posts

    26
  • Joined

  • Last visited

Everything posted by atilla.gahbro

  1. anybody know a way to modify the text in the drop down menu items in the support ticket post reply section? please see the attached screen shot i looked in the language files but could not locate it thanks
  2. yeah i know but unless you do that i dont see how it can be a part of a specific customer manually managing a folder and subfolders on the server would not be too desirable on another note, i found this: http://tinymce.moxiecode.com/plugins_filemanager.php its the same people who make the html editor for the kb section of whmcs itself i know its just a file manager and does nto make the files a part of a specific customer but i am just looking for any ideas on how we might use this in some way thanks in advance
  3. tomdchi, did you get around to writing a delete function for this script?
  4. direct from the horse's mouth: ********************************************************** http://www.whmcs.com/otheruses.php Other Uses WHMCS isn't just for web hosts. Here are just a selection of other uses that WHMCS is being put to: * Web Design Clients Invoicing * Automated Recurring Billing for Membership Sites * Dedicated Server Sales * Software Products What few people realise is that WHMCS does not need to be tied into any servers to function. It can function perfectly fine as a billing system without utilising any of the automatic provisioning functions. And of course there's the support system which you can use to keep communication with clients organised. With the flexible one time invoicing, product options, addons and promotions system you won't be limited by WHMCS for your invoicing and selling needs. If you are interested in finding out more about just how WHMCS could work for your business, feel free to contact us. ********************************************************** seems to me that the door is some what open here
  5. we recently started flagging tickets to a user called "need-to-bill" and keeping track of billable support incidents that way. its not the greatest but it works for now.
  6. we use the mobile carriers' email-to-sms gateways and just create an additional staff member and set it to be notified for that department examples: sprint uses phonenumber@messaging.sprintpcs.com metropcs uses phonenumber@mymetropcs.com they all have one even the bargain basement ones like metropcs we use this all day and it works good for us if you dont want to worry about sms code
  7. here is what i did. setup a dedicated subdomain for the email domain with its own mail server and set it up to not send ndrs now the only mail coming back are replies but the auto responders from the recepients are still going to be a problem i wish whmcs had a subject line filter so we could filter out subjects like [AUTO REPLY] and not consider them customer replies. maybe i will add it to the feature request section... thanks
  8. currently in our whmcs installation when an email sent to a customer bounces for whatever reason whmcs creates another ticket because the ndr comes back to the department mailbox anyone know a way to suppress this behavior?
  9. the quotation system is great for a one off incident or a sale of some systems but for routine support that does not need to be pre authed or where the exact amount is unknown it does not really represent the operational flow of that incident. support outside of situations included in a hosting package quite often starts as a support ticket but then gets to a point where its something in between a quote, an order and an invoice. its this middle ground that is not covered by whmcs currently. i noticed in the quote system in 3.8 we can set the quote as accepted and generate an invoice. all we would need is the ability to give an admin the ability to check a box for a support ticket to flag it as billable and when the invoice is generated referencing that ticket the ticket would get closed out. that wo-uld be the app level check to insure that it gets billed. if its flagged as billable an invoice is what it would take to close the ticket. i know i am partially oversimplifying it but whmcs already has a similar logic in the quoting system. i personally know of many companies that are both hosts and managed service providers that always complain of this problem. as a secondary problem when you use an ternal billing system there never seems to be enough detail of the work performed for the person who is getting the bill. then if you copy and paste ticket notes in to the invoice you run the risk of sometimes pasting internal notes that may not have been for the customer's eyes...
  10. this is an interesting topic. i can see all of the different opinions on this subject. its almost like religion and politics... what i think is evident is that everyone uses whmcs in different ways. yes the majority are straight hosting providers and many of the comments are coming from that angle. in our case we dont even charge for hosting. we are not even a "hosting company" but rather an integrated services company providing t1/t3 (the slow brother of the e variant for you overseas dudes) access with voip and many other bundled services. why do we use whmcs? because it is the one product we have found that can integrate with other apps using modules and also has an internal kb, ticketing, orders, etcetera, etcetera... in our business model issues can go from the public ip entry point in to the customers local network real quickly. unless the customer is on a support plan (which we intend on using the licensing module to bill for) we charge for every minute of support and do so at a high rate just to cover our costs for providing the service. if we did not we would be breaking even at the end of the month. even with that model we still miss support tickets that should have been billed for because in our current system there is nothing but the human element to catch those tickets. no application level checks to catch such tickets. our msa and tos state that any issues we are asked to work on are billable if the source of the problem that we "resolve" is on the customer owned systems. so we do not need a preauth to generate an invoice after the support ticket is closed. i read in one of the earlier posts where someone suggested that a provider who charges for support will not be in business very long. the exact opposite is true. in a culture of free everything mentality only the googles of the world with indirect revenue streams can partake of such unorthodox practices. i'll say it now and hopefully matt reads this. if whmcs creates a module to flag tickets as "billable" at the first reply from an admin, then we will but that module. sold. we'll even pay in advance. by the way comments are not worth $5.00 or even $3.00 but they are amusing. on the other hand great support for operation effecting issues is worth something to customers. and needs to be billed for... in our model at least.
  11. i think it looks nice and clean i prefer the portal template based designs on our site which is still under development http://portal.subrigo.net we chose to use the icons from the default template as they seemed nicer but we kept the portal layout my strictly personal opinions: 1- the portal name should be customer portal and not support 2- announcements should be news/annoucements 3- network status should never be called network issues 4- the kb and tutorials should be managed in a similar way 5- much of the whmcs template is confusing so the descriptions need to be modified to simplify the interface for users let me know what you think of our site going to go live in jan-2009 good work on your site atilla
  12. i took Zorro67's advice and used the kb section of whmcs so it could be referenced for tickets in replies and have some structure within the system http://portal.subrigo.net/knowledgebase.php
  13. we use demowolf tutorials as well and just rolled out whmcs we decided to tie the flash videos in to the knowledgebase feature of whmcs because that is the only way it could be referenced for support tickets in an integrated manner outside of manually copying and pasting urls. even though all items under the knowledgebase are technically referred to as articles we relabeled the knowledgebase on the front end as "knowledgebase/tutorials" and set the top level to two sections as "knowledgebase" and "video tutorials". we then break it down further from there. you can see it at: http://portal.subrigo.net/knowledgebase.php if anyone has a better way to do this i am all ears. thanks
  14. we need to have whmcs index customers by the company name instead of the first and last name of the primary contact anyone know if this is somehow possible?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated