Not yet, but it will in the future. Our first iteration was to focus on inputting mobile leads for our customers who own and operate themselves on the go, and updates to the app are going to build in more functionality for the workers to view and manage their schedule. A calendar would be part of that.
Not yet, but it will in the future. Our first iteration was to focus on inputting mobile leads for our customers who own and operate themselves on the go, and updates to the app are going to build in more functionality for the workers to view and manage their schedule. A calendar would be part of that.
We gave up on day-one with the app for this reason...on an Android anyway, if we accidentally hit 'back' instead of using the on-screen navigation, it closes the app. Then upon re-open, we have to enter login info again. Figured you guys would get to it, but the password issue is not an apple-only issue
We gave up on day-one with the app for this reason...on an Android anyway, if we accidentally hit 'back' instead of using the on-screen navigation, it closes the app. Then upon re-open, we have to enter login info again. Figured you guys would get to it, but the password issue is not an apple-only issue
We understand. It's simply a speed/data hurdle that we were not able to accomplish yet. It's in our roadmap for the future. Just keep an eye on our release notes to know when you can start taking advantage of it.
We understand. It's simply a speed/data hurdle that we were not able to accomplish yet. It's in our roadmap for the future. Just keep an eye on our release notes to know when you can start taking advantage of it.
Don't take this as a "garaunteed release date" because unexpected things can come up when it comes to creating new features, but it's in our development teams roadmap for completing in the next few weeks.
Don't take this as a "garaunteed release date" because unexpected things can come up when it comes to creating new features, but it's in our development teams roadmap for completing in the next few weeks.
We added 'save copy' as a work-around for this. So you look up a lead for a previous customer, edit it and at the bottom left hit 'save copy'. Now you'll leave the original lead alone and have a new one with all the customer info entered.
We added 'save copy' as a work-around for this. So you look up a lead for a previous customer, edit it and at the bottom left hit 'save copy'. Now you'll leave the original lead alone and have a new one with all the customer info entered.
I am sure you've thought this through, but have you considered simply making the back-end of IO responsive/mobile friendly? This way, all functionality is there and you're not having to maintain an app as well?
I am sure you've thought this through, but have you considered simply making the back-end of IO responsive/mobile friendly? This way, all functionality is there and you're not having to maintain an app as well?
Yes, the leads page will eventually get a facelift, but the app does have other advantages native to mobile devices such as alerting and GPS function that we intent to take advantage of.
Yes, the leads page will eventually get a facelift, but the app does have other advantages native to mobile devices such as alerting and GPS function that we intent to take advantage of.
Any new updates planned for the app? For our workers, it would be great if they could use the app to access attachments and directions to their event. Currently it appears those are only accessible through the "leads" list, but workers only have access to the "shifts" list. They can at least get packing lists from there, but not much else that's helpful to them.
Also would be good if we had backend permissions control over what they can see. We prefer to not let our event techs see contracts and quotes (they don't really need to know what we're charging the clients). So we setup the workers site that way. But on the app, they have easy access to contracts for each shift anyway.
Any new updates planned for the app? For our workers, it would be great if they could use the app to access attachments and directions to their event. Currently it appears those are only accessible through the "leads" list, but workers only have access to the "shifts" list. They can at least get packing lists from there, but not much else that's helpful to them.
Also would be good if we had backend permissions control over what they can see. We prefer to not let our event techs see contracts and quotes (they don't really need to know what we're charging the clients). So we setup the workers site that way. But on the app, they have easy access to contracts for each shift anyway.
Yes, we have some planned updates for the app. The initial development focused on just being able to do some basic leads things on the go, and we intend to add more worker function/control as it develops more.
Yes, we have some planned updates for the app. The initial development focused on just being able to do some basic leads things on the go, and we intend to add more worker function/control as it develops more.
Not yet, but it will in the future. Our first iteration was to focus on inputting mobile leads for our customers who own and operate themselves on the go, and updates to the app are going to build in more functionality for the workers to view and manage their schedule. A calendar would be part of that.
Not yet, but it will in the future. Our first iteration was to focus on inputting mobile leads for our customers who own and operate themselves on the go, and updates to the app are going to build in more functionality for the workers to view and manage their schedule. A calendar would be part of that.
Sounds good! Thank you for your help. Do you think that it would be possible to accept payments with the app?
Sounds good! Thank you for your help. Do you think that it would be possible to accept payments with the app?
Could you also integrate the app to remember login information and to use Touch ID on IOS devices?
Could you also integrate the app to remember login information and to use Touch ID on IOS devices?
The app really needs to pull/fetch data, specifically previous customers information. Without this the app is pretty much useless for us.
The app really needs to pull/fetch data, specifically previous customers information. Without this the app is pretty much useless for us.
I am sure you've thought this through, but have you considered simply making the back-end of IO responsive/mobile friendly? This way, all functionality is there and you're not having to maintain an app as well?
I am sure you've thought this through, but have you considered simply making the back-end of IO responsive/mobile friendly? This way, all functionality is there and you're not having to maintain an app as well?
Any new updates planned for the app? For our workers, it would be great if they could use the app to access attachments and directions to their event. Currently it appears those are only accessible through the "leads" list, but workers only have access to the "shifts" list. They can at least get packing lists from there, but not much else that's helpful to them.
Also would be good if we had backend permissions control over what they can see. We prefer to not let our event techs see contracts and quotes (they don't really need to know what we're charging the clients). So we setup the workers site that way. But on the app, they have easy access to contracts for each shift anyway.
Any new updates planned for the app? For our workers, it would be great if they could use the app to access attachments and directions to their event. Currently it appears those are only accessible through the "leads" list, but workers only have access to the "shifts" list. They can at least get packing lists from there, but not much else that's helpful to them.
Also would be good if we had backend permissions control over what they can see. We prefer to not let our event techs see contracts and quotes (they don't really need to know what we're charging the clients). So we setup the workers site that way. But on the app, they have easy access to contracts for each shift anyway.
Replies have been locked on this page!